Triple
T19331080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victoria Highway |
E483493
|
entity |
| Predicate | easternJunction |
P86489
|
FINISHED |
| Object | Stuart Highway at Katherine |
—
|
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: Stuart Highway at Katherine | Statement: [Victoria Highway, easternJunction, Stuart Highway at Katherine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: easternJunction Context triple: [Victoria Highway, easternJunction, Stuart Highway at Katherine]
-
A.
easternTerminusLocatedOn
chosen
Indicates that the eastern endpoint of a route, line, or path is situated on or at a specified feature or location.
-
B.
easternTerminusTown
Indicates that a given town serves as the eastern endpoint or terminus of a route, line, or corridor.
-
C.
easternBaseOf
Indicates that one entity is located at or forms the eastern base or foot of another entity.
-
D.
easternmostPartOf
Indicates that one entity is the geographically furthest-east portion or segment of another entity.
-
E.
easternConnection
Indicates a relationship where one entity is connected to, aligned with, or positioned toward the east of another 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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e616412bcc81909bb34d3cf5363129 |
completed | April 20, 2026, 12:04 p.m. |
| PD | Predicate disambiguation | batch_69e4dd12303c8190a2027c062b2dff40 |
completed | April 19, 2026, 1:48 p.m. |
Created at: April 10, 2026, 1:33 p.m.