Triple
T2108330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Network Time Protocol |
E42445
|
entity |
| Predicate | version |
P3286
|
FINISHED |
| Object | NTPv1 |
E42445
|
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: NTPv1 | Statement: [Network Time Protocol, version, NTPv1]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: NTPv1 Context triple: [Network Time Protocol, version, NTPv1]
-
A.
Network Time Protocol
chosen
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.
-
B.
SNMPv1
SNMPv1 is the first version of the Simple Network Management Protocol, used for basic network device monitoring and management over IP networks.
-
C.
RFC 868
RFC 868 is an Internet standard that specifies the Time Protocol, a simple service for transmitting the time over a network.
-
D.
IEEE 1588 Precision Time Protocol standard
The IEEE 1588 Precision Time Protocol standard defines a method for highly accurate time synchronization over packet-based networks, widely used in industrial automation, telecommunications, and power systems.
-
E.
RFC 1901
RFC 1901 is an IETF standards document that specifies the community-based version of the Simple Network Management Protocol, commonly known as SNMPv2c.
- 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_69a8871040f08190aac2e2d0ab6b47ad |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbae03f308190841f5a419bb821f6 |
completed | March 7, 2026, 5:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae306ff3a481909ce3c34edb3ab0e2 |
completed | March 9, 2026, 2:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.