Triple
T9121747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R102 regional road |
E218867
|
entity |
| Predicate | parallelsRoute |
P19597
|
FINISHED |
| Object | N2 highway |
—
|
NE NERFINISHED |
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: N2 highway | Statement: [R102 regional road, parallelsRoute, N2 highway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parallelsRoute Context triple: [R102 regional road, parallelsRoute, N2 highway]
-
A.
parallelRoute
chosen
Indicates that one route runs alongside and in the same general direction as another route without intersecting it.
-
B.
routesFrom
Indicates that something (such as a path, connection, or communication) originates at one entity and is directed or carried from that source entity toward another.
-
C.
routeBetween
Indicates that there exists a path or connection enabling travel or communication between two locations or points.
-
D.
routeVia
Indicates that a connection, path, or communication between two points is established or carried out through an intermediate location, node, or channel.
-
E.
tradRoutes
Indicates a relationship where one location serves as a trade route to or from another location, facilitating the movement of goods or commerce between them.
- 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_69ca83dddd548190983b96c664f7f367 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8b46dac8190bde88205c85f596a |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc66003e3c819091e1e42c9cf7c781 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:17 p.m.