Triple

T9874531
Position Surface form Disambiguated ID Type / Status
Subject Outwood railway station E240040 entity
Predicate serves P98 FINISHED
Object Outwood E826676 NE 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: Outwood | Statement: [Outwood railway station, serves, Outwood]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Outwood
Context triple: [Outwood railway station, serves, Outwood]
  • A. Outwood chosen
    Outwood is a village and suburb in West Yorkshire, England, situated between Wakefield and Leeds.
  • B. Scotswood
    Scotswood is a district in the west end of Newcastle upon Tyne, England, historically known for its industrial heritage and riverside location on the River Tyne.
  • C. Whitwood
    Whitwood is a residential and industrial area in West Yorkshire, England, situated on the outskirts of the town of Castleford.
  • D. Burtonwood
    Burtonwood is a village in Cheshire, England, historically associated with coal mining and the former RAF Burtonwood airbase.
  • E. Simonswood
    Simonswood is a small rural village and civil parish in Lancashire, England, known for its agricultural landscape and quiet countryside character.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69ca84e8a0788190b9061811d50fd554 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cdb3f89fa081908b58956902c193cf completed April 2, 2026, 12:10 a.m.
NED1 Entity disambiguation (via context triple) batch_69d1eae5a31c81908085f637fbbff6d2 completed April 5, 2026, 4:53 a.m.
Created at: March 30, 2026, 8:37 p.m.