Triple
T3680108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parkes |
E78089
|
entity |
| Predicate | railJunction |
P14468
|
FINISHED |
| Object | Newell Highway freight routes |
—
|
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: Newell Highway freight routes | Statement: [Parkes, railJunction, Newell Highway freight routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railJunction Context triple: [Parkes, railJunction, Newell Highway freight routes]
-
A.
railwayJunctionFor
chosen
Indicates that a location serves as a junction point where multiple railway lines or routes connect or intersect for a given railway network or service.
-
B.
railTracks
Indicates that one entity consists of, includes, or is associated with rail tracks used for guiding trains or rail vehicles.
-
C.
transportationJunctionFor
Indicates a location that serves as a connecting point where multiple transportation routes or modes meet, intersect, or transfer.
-
D.
junctionStation
Indicates that a station functions as a junction where multiple routes or lines intersect or connect.
-
E.
railComponent
Indicates a relationship where one entity is a structural or functional part of a rail or railway system component 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_69ad85e18c1c8190be8aafb227f39f48 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc49153ec81909ff3a3df54416d0e |
completed | March 8, 2026, 6:48 p.m. |
| PD | Predicate disambiguation | batch_69adb84be1fc81909721c871babb4633 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:25 p.m.