Triple

T16864570
Position Surface form Disambiguated ID Type / Status
Subject Corrour railway station E410005 entity
Predicate locatedIn P40 FINISHED
Object Corrour E410005 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: Corrour | Statement: [Corrour railway station, locatedIn, Corrour]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Corrour
Context triple: [Corrour railway station, locatedIn, Corrour]
  • A. Corrour chosen
    Corrour is a remote Scottish Highland railway station and estate, famed for being one of the most isolated stops in the UK rail network and for its dramatic surrounding scenery.
  • B. Elmora
    Elmora is a residential neighborhood within the city of Elizabeth in Union County, New Jersey.
  • C. Rintoul
    Rintoul is a Scottish-origin surname borne by various notable figures, including journalists, actors, and politicians.
  • D. Larimore
    Larimore is a small city in eastern North Dakota, United States, known for its rural character and proximity to Grand Forks.
  • E. Durkee
    Durkee is a small historic unincorporated community in Baker County, Oregon, that developed as a stage stop and later a railroad and highway point along key transportation routes.
  • 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_69d88395e6c88190b22730f335107c14 completed April 10, 2026, 4:59 a.m.
NER Named-entity recognition batch_69e3b506dd1c81909ab8006b6a1e2b7a completed April 18, 2026, 4:44 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00bb294c0481908306e1f604cc7404 completed May 10, 2026, 5:06 p.m.
Created at: April 10, 2026, 5:24 a.m.