Triple
T22219022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A13 motorway (Portugal) |
E549156
|
entity |
| Predicate | startJunction |
P147339
|
FINISHED |
| Object | A23 motorway |
—
|
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: A23 motorway | Statement: [A13 motorway (Portugal), startJunction, A23 motorway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startJunction Context triple: [A13 motorway (Portugal), startJunction, A23 motorway]
-
A.
servesJunction
Indicates that one element functions as a connecting or branching point where multiple other elements meet or intersect.
-
B.
terminusJunction
Indicates a relationship where a route, line, or path ends at a junction point that serves as its terminal connection.
-
C.
junctionStation
Indicates that a station functions as a junction where multiple routes or lines intersect or connect.
-
D.
wasJunctionFor
Indicates that one entity functioned as a junction or connecting point for another entity, typically serving as an intersection or hub through which the other entity passed or was routed.
-
E.
startsAtRoad
Indicates that something begins or originates at a specific road or roadway location.
- 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_69e11e403d6481909a94d0aaf157f6ef |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12b8edd288190a49f10e009122057 |
completed | April 28, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69e71b4dcc408190a30429fb08fcf39e |
completed | April 21, 2026, 6:38 a.m. |
| PDg | Predicate description generation | batch_69e723f65c5c8190a0ee3c539e5d0767 |
completed | April 21, 2026, 7:15 a.m. |
Created at: April 16, 2026, 8:37 p.m.