Triple
T9690776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 5905 |
E234528
|
entity |
| Predicate | protocolVersionDefined |
P11574
|
FINISHED |
| Object | NTPv4 |
—
|
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: NTPv4 | Statement: [RFC 5905, protocolVersionDefined, NTPv4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protocolVersionDefined Context triple: [RFC 5905, protocolVersionDefined, NTPv4]
-
A.
protocolVersion
Indicates the specific version of a protocol that governs how two or more entities communicate or interact.
-
B.
protocolDefined
Indicates that a specific protocol formally specifies or governs the behavior, format, or interaction associated with the related entities.
-
C.
protocolNumber
Indicates the specific identifying number assigned to a protocol that governs or documents an interaction, process, or agreement between entities.
-
D.
protocolName
Indicates the specific communication or interaction protocol used or associated with an entity or connection.
-
E.
specifiesProtocolVersion
chosen
Indicates that an entity defines or sets the particular protocol version to be used in a communication or interaction.
- F. None of above.
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_69ca84ca73208190957a900c8543bdcc |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d0422e88190a234ba74eb0dad25 |
completed | April 1, 2026, 10:32 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b840f081909f66bf0b66d17d9b |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:17 p.m.