Triple
T31947939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 5906 |
E815701
|
entity |
| Predicate | definesProtocolMechanismFor |
P12564
|
FINISHED |
| Object | Network Time Protocol |
—
|
NE NERFINISHED |
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: Network Time Protocol | Statement: [RFC 5906, definesProtocolMechanismFor, Network Time Protocol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesProtocolMechanismFor Context triple: [RFC 5906, definesProtocolMechanismFor, Network Time Protocol]
-
A.
definesMechanism
Indicates that one entity specifies or explains the underlying process or mechanism by which another entity operates or occurs.
-
B.
createsMechanismFor
Indicates that one entity brings about or establishes a means, process, or structure that enables or facilitates a particular function or outcome for another entity.
-
C.
authenticationProtocol
Indicates that a particular method or set of rules is used to verify the identity of an entity before granting access or performing an action.
-
D.
specifiesProtocol
chosen
Indicates that one entity defines or designates the communication or interaction protocol to be used by another entity.
-
E.
specifiesProtocolExtensionFor
Indicates that one protocol extension defines or constrains the behavior, capabilities, or usage of another protocol.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd8e5f7c4c8190ab8e2f2a7bb1bd79 |
completed | May 8, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fd8d8a16f08190b9e880901bfa44fe |
completed | May 8, 2026, 7:15 a.m. |
Created at: May 1, 2026, 12:07 a.m.