Triple
T5479051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IP |
E123425
|
entity |
| Predicate | routingBasedOn |
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: [IP, routingBasedOn, destination IP address]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routingBasedOn Context triple: [IP, routingBasedOn, destination IP address]
-
A.
routingBasis
chosen
Indicates the principle or criterion used to determine how something is directed, routed, or assigned among possible paths or destinations.
-
B.
routeVia
Indicates that a connection, path, or communication between two points is established or carried out through an intermediate location, node, or channel.
-
C.
routeTargeted
Indicates that a route is specifically directed toward or intended to reach a particular target entity or destination.
-
D.
route
Indicates that one entity serves as a path or course used to travel or move between locations associated with another entity.
-
E.
approachRoute
Indicates the path or method taken by one entity as it moves toward or comes closer to another entity or target.
- 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9247a16c8190ac5a02534da48853 |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd91a58c448190904964a439045e05 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.