Triple
T21091657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Routing Information Protocol |
E519652
|
entity |
| Predicate | metricMaximumHopCount |
P14301
|
FINISHED |
| Object | 15 |
—
|
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: 15 | Statement: [Routing Information Protocol, metricMaximumHopCount, 15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metricMaximumHopCount Context triple: [Routing Information Protocol, metricMaximumHopCount, 15]
-
A.
maximumNetworkSpanWithRepeaters
Indicates the greatest distance a network signal can reliably cover when using repeaters to extend its range.
-
B.
networkLength
Indicates the total measured extent or distance covered by a network (e.g., of connections, links, or paths).
-
C.
maximumReach
chosen
Indicates the greatest extent, distance, or limit that something can reach or influence within a given context.
-
D.
isHopByHop
Indicates that the relationship or process occurs stepwise between directly connected intermediaries, with each node handling and forwarding it to the next rather than end-to-end.
-
E.
maxSingleCanalLength
Indicates the maximum length of any single canal segment associated with an entity.
- 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.