Triple
T35970658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sydney–Wollongong–Nowra corridor |
E1040275
|
entity |
| Predicate | mainRailRoute |
P109925
|
FINISHED |
| Object | South Coast Line |
—
|
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: South Coast Line | Statement: [Sydney–Wollongong–Nowra corridor, mainRailRoute, South Coast Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainRailRoute Context triple: [Sydney–Wollongong–Nowra corridor, mainRailRoute, South Coast Line]
-
A.
hasRailRoute
Indicates that there exists a rail-based transportation route or connection between the related entities.
-
B.
primaryRailLinkFor
chosen
Indicates that one entity serves as the main or principal rail connection or route for another entity.
-
C.
majorRouteTo
Indicates that one location serves as a primary or significant route or pathway leading to another location.
-
D.
routeOf
Indicates that one entity is the path, course, or trajectory taken or followed by another entity (such as a vehicle, shipment, or signal).
-
E.
primaryMarketedRouteName
Indicates the main route or method by which a product is marketed or delivered to its intended users.
- 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_69f7b2c771108190adeec151daad5dab |
completed | May 3, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:07 p.m.