Triple
T35970656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sydney–Wollongong–Nowra corridor |
E1040275
|
entity |
| Predicate | mainRoadRoute |
P5943
|
FINISHED |
| Object | Princes 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: Princes Highway | Statement: [Sydney–Wollongong–Nowra corridor, mainRoadRoute, Princes Highway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainRoadRoute Context triple: [Sydney–Wollongong–Nowra corridor, mainRoadRoute, Princes Highway]
-
A.
roadName
chosen
Indicates the specific name assigned to a road that identifies it within a transportation or address system.
-
B.
majorRouteTo
Indicates that one location serves as a primary or significant route or pathway leading to another location.
-
C.
mainRoadInfrastructure
Indicates that a road segment functions as a primary or major route within the transportation infrastructure network.
-
D.
roadMode
Indicates the mode or type of transportation being used on a road within the described relationship or action.
-
E.
routeOf
Indicates that one entity is the path, course, or trajectory taken or followed by another entity (such as a vehicle, shipment, or signal).
- 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_69f76e27758c81909b711cf38a130aaf |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7acaec1508190a38f2ac9cc5383e7 |
completed | May 3, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.