Triple
T26398882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 7868 |
E663646
|
entity |
| Predicate | definesProtocolStatus |
P101079
|
FINISHED |
| Object | informational routing protocol |
—
|
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: informational routing protocol | Statement: [RFC 7868, definesProtocolStatus, informational routing protocol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesProtocolStatus Context triple: [RFC 7868, definesProtocolStatus, informational routing protocol]
-
A.
hasProtocolStatus
Indicates that an entity is associated with a particular protocol-related state or condition it currently holds.
-
B.
definedStatusFor
chosen
Indicates that one entity establishes or specifies the status or state assigned to another entity.
-
C.
protocolDefined
Indicates that a specific protocol formally specifies or governs the behavior, format, or interaction associated with the related entities.
-
D.
specifiesProtocol
Indicates that one entity defines or designates the communication or interaction protocol to be used by another entity.
-
E.
hasProtocolRole
Indicates that an entity participates in a protocol by fulfilling a specific role or function within that 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_69ee883823988190b418b111be28a44a |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 26, 2026, 11:30 p.m.