Triple

T2429442
Position Surface form Disambiguated ID Type / Status
Subject Pilbara region E52806 entity
Predicate railInfrastructure P848 FINISHED
Object heavy haul railways for iron ore 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 railways for iron ore | Statement: [Pilbara region, railInfrastructure, heavy haul railways for iron ore]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: railInfrastructure
Context triple: [Pilbara region, railInfrastructure, heavy haul railways for iron ore]
  • A. usesRailInfrastructureOf
    Indicates that one entity operates on, accesses, or otherwise makes use of the rail infrastructure owned or managed by another entity.
  • B. railTracks
    Indicates that one entity consists of, includes, or is associated with rail tracks used for guiding trains or rail vehicles.
  • C. railwayLine chosen
    Indicates that there is a railway line connection or route associated with or passing through the referenced entity.
  • D. railroadNetwork
    Indicates a relationship where locations are connected as part of the same system of railway lines and infrastructure used for train transport.
  • E. railroadMet
    Indicates that two or more railroads encountered or connected with each other at a specific place or time.
  • 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_69ab4959bcc0819083246f9fb10439e3 completed March 6, 2026, 9:38 p.m.
NER Named-entity recognition batch_69abcc74a5108190a3a9631b0cc1a127 completed March 7, 2026, 6:57 a.m.
PD Predicate disambiguation batch_69abc5aa1b60819081b87f7985c6cff3 completed March 7, 2026, 6:28 a.m.
Created at: March 6, 2026, 9:43 p.m.