Triple
T2581911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Hedland |
E57109
|
entity |
| Predicate | railUse |
P33182
|
FINISHED |
| Object | heavy-haul iron ore trains |
—
|
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: heavy-haul iron ore trains | Statement: [Port Hedland, railUse, heavy-haul iron ore trains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railUse Context triple: [Port Hedland, railUse, heavy-haul iron ore trains]
-
A.
railwayUse
Indicates that something is used as, or functions in the capacity of, a railway or rail-based transportation facility.
-
B.
usesRailInfrastructureOf
Indicates that one entity operates on, accesses, or otherwise makes use of the rail infrastructure owned or managed by another entity.
-
C.
formerRailUse
Indicates that an entity previously served a particular railway-related function or purpose, but no longer does so.
-
D.
railroadMet
Indicates that two or more railroads encountered or connected with each other at a specific place or time.
-
E.
railwayLineUsage
chosen
Indicates how a railway line is used, such as the type or purpose of traffic or operations it supports.
- 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_69ab4a4dca6481908c301f8e317396e7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd3c843bc8190837cea3441bf3ca1 |
completed | March 7, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69abd0cfeae08190aed03866ba071c5c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.