Triple
T18799976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puffy |
E459733
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | OpenNTPD |
E911263
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: OpenNTPD | Statement: [Puffy, relatedTo, OpenNTPD]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: OpenNTPD Context triple: [Puffy, relatedTo, OpenNTPD]
-
A.
OpenNTPD
chosen
OpenNTPD is a secure, lightweight implementation of the Network Time Protocol designed for simplicity and code correctness, originating from the OpenBSD project.
-
B.
NTP
NTP is a Saudi Arabian government initiative aimed at diversifying the economy and enhancing public sector efficiency as part of the broader Vision 2030 reform agenda.
-
C.
NTP
NTP is a U.S. interagency program that evaluates environmental substances for potential toxic and carcinogenic effects on human health.
-
D.
NTP Autokey
NTP Autokey is a cryptographic authentication and key management protocol designed to secure time synchronization in the Network Time Protocol (NTP).
-
E.
Network Time Protocol
Network Time Protocol (NTP) is a widely used networking protocol designed to synchronize the clocks of computers and devices over packet-switched, variable-latency data networks.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a02273b481909bc250144a0ace32 |
completed | April 20, 2026, 3:40 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a054723def4819097961a04087a54a3 |
completed | May 14, 2026, 3:53 a.m. |
Created at: April 10, 2026, 11:53 a.m.