Triple

T26583641
Position Surface form Disambiguated ID Type / Status
Subject Adra Junction E667144 entity
Predicate railwayDivisionHQFor P31350 FINISHED
Object Adra railway division NE NERFINISHED

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: Adra railway division | Statement: [Adra Junction, railwayDivisionHQFor, Adra railway division]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: railwayDivisionHQFor
Context triple: [Adra Junction, railwayDivisionHQFor, Adra railway division]
  • A. railwayDivisionHeadquartersOf chosen
    Indicates that one location serves as the administrative headquarters for a specified railway division.
  • B. railwayDivision
    Indicates that one administrative railway division is responsible for, manages, or encompasses another railway unit, line, or area within a rail network.
  • C. railwayZoneHeadquartersFor
    Indicates that a location serves as the administrative headquarters for a particular railway zone.
  • D. railroadSubdivision
    Indicates that one railroad line or territory is a designated subdivision (operational segment) of a larger railroad network.
  • E. hasRailwayHeadquarters
    Indicates that a railway organization or system has its main administrative or operational headquarters located at a specified place.
  • 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_69ee9cfb7e548190b60a9031182f5a7e completed April 26, 2026, 11:17 p.m.
NER Named-entity recognition batch_69f657f653448190a945b4751af8507d completed May 2, 2026, 8 p.m.
PD Predicate disambiguation batch_69f6575ba12081909396036f78757a76 completed May 2, 2026, 7:58 p.m.
Created at: April 27, 2026, 2:04 a.m.