Triple
T31968541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1119 |
E816244
|
entity |
| Predicate | successorProtocolVersion |
P199127
|
FINISHED |
| Object | NTPv3 |
—
|
LITERAL 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: NTPv3 | Statement: [RFC 1119, successorProtocolVersion, NTPv3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorProtocolVersion Context triple: [RFC 1119, successorProtocolVersion, NTPv3]
-
A.
successorProtocol
Indicates that one protocol directly follows and replaces another in sequence or versioning.
-
B.
successorProtocolFamily
Indicates that one protocol family directly follows and replaces another in a sequence or evolution of related protocols.
-
C.
protocolVersion
Indicates the specific version of a protocol that governs how two or more entities communicate or interact.
-
D.
successorCode
Indicates that one code directly follows and replaces another code in a defined sequence or versioning scheme.
-
E.
successorStructureIntroducedIn
Indicates that a particular successor structure was first introduced or defined in a specified source, context, or work.
- F. None of above. chosen
Provenance (4 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_69f348f5ae5481909da0247869f51955 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff21cbd9108190a52c0ba42004c669 |
completed | May 9, 2026, noon |
| PD | Predicate disambiguation | batch_69ff1faea91881908c626c70bca5100a |
completed | May 9, 2026, 11:51 a.m. |
| PDg | Predicate description generation | batch_69ff21ca6964819088bdf1810b7863f2 |
completed | May 9, 2026, noon |
Created at: May 1, 2026, 12:10 a.m.