Triple
T22062079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 7503 |
E545177
|
entity |
| Predicate | routingProtocolType |
P31502
|
FINISHED |
| Object | link-state 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: link-state routing protocol | Statement: [RFC 7503, routingProtocolType, link-state routing protocol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routingProtocolType Context triple: [RFC 7503, routingProtocolType, link-state routing protocol]
-
A.
routingProtocol
chosen
Indicates that one entity uses, implements, or is associated with a specific routing protocol to determine paths for forwarding data in a network.
-
B.
routingCapability
Indicates the ability of an entity to determine and direct the path that data, messages, or items should take through a network or system.
-
C.
routeNetworkType
Indicates the specific kind of transportation or communication network to which a route belongs (e.g., road, rail, or air).
-
D.
routingDomainType
Indicates the classification or category of routing domain associated with a given routing configuration or relationship.
-
E.
transportProtocol
Indicates the communication protocol used to transport data between entities in a networked 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_69e11e3377c48190890c17407b9527d6 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1285d5e508190b3124a70fe55b32e |
completed | April 28, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69e6f643ca74819083e8ab78e843f243 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:27 p.m.