Triple
T394755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internet Protocol |
E8957
|
entity |
| Predicate | routingBasis |
P12563
|
FINISHED |
| Object | destination IP address |
—
|
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: destination IP address | Statement: [Internet Protocol, routingBasis, destination IP address]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routingBasis Context triple: [Internet Protocol, routingBasis, destination IP address]
-
A.
route
Indicates that one entity serves as a path or course used to travel or move between locations associated with another entity.
-
B.
routeCategory
Indicates the classification or type assigned to a route within a transportation or path network.
-
C.
parentRoute
Indicates that one route serves as the direct hierarchical ancestor or container of another route within a routing structure.
-
D.
approachRoute
Indicates the path or method taken by one entity as it moves toward or comes closer to another entity or target.
-
E.
followsRouteOf
Indicates that one entity travels along the same path or route that another entity takes or has taken.
- F. None of above. chosen
Provenance (4 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_69a2e7f55c60819097aff65ea2ca2832 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec77a8a08190b6f96373aa8c1346 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e96bd3848190a66ca14dfbd26da5 |
completed | Feb. 28, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69a2ea7d03a88190aab72e61d8673488 |
completed | Feb. 28, 2026, 1:15 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.