Triple
T21091656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Routing Information Protocol |
E519652
|
entity |
| Predicate | usesRoutingMetric |
P1459
|
FINISHED |
| Object | hop count |
—
|
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: hop count | Statement: [Routing Information Protocol, usesRoutingMetric, hop count]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRoutingMetric Context triple: [Routing Information Protocol, usesRoutingMetric, hop count]
-
A.
usesRoutingType
Indicates that one entity employs or operates according to a specific routing type or routing method associated with another entity.
-
B.
supportsHierarchicalRouting
Indicates that one entity enables or is compatible with routing that uses a multi-level or hierarchical structure of routing domains or paths.
-
C.
supportsRouting
Indicates that one entity provides the capability to determine and direct paths or routes for another entity’s traffic, requests, or messages.
-
D.
usedRoutes
Indicates that an entity has utilized or traveled along specific routes.
-
E.
usesMetric
chosen
Indicates that one entity adopts, applies, or relies on a particular metric or measurement standard in its operation, evaluation, or description.
- 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_69e0b507dd9081908fb8bfcbef4c8b46 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7094f6ebc8190a90b014755a9d4a6 |
completed | April 21, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69e5dbfcd5e881908f1e4e0d2d237856 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:51 p.m.