Triple

T24787879
Position Surface form Disambiguated ID Type / Status
Subject Finley railway precinct E620166 entity
Predicate relationshipToTownship P160816 FINISHED
Object served as primary rail gateway for Finley 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: served as primary rail gateway for Finley | Statement: [Finley railway precinct, relationshipToTownship, served as primary rail gateway for Finley]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: relationshipToTownship
Context triple: [Finley railway precinct, relationshipToTownship, served as primary rail gateway for Finley]
  • A. landRelation
    Indicates a spatial or ownership-based relationship between entities and a specific piece or area of land.
  • B. relationshipToVillagers
    Indicates the nature or type of relationship that an entity has with the villagers.
  • C. hasTownship
    Indicates that one administrative area or jurisdiction includes or is associated with a specific township.
  • D. typeOfMunicipalRelationship
    Indicates a formal type or category of administrative or cooperative relationship that exists between municipalities.
  • E. relationshipToState
    Indicates a relationship or connection that an entity has with a particular state or governmental body.
  • F. None of above. chosen

Provenance (4 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_69e2fabdbe8c8190adbb9434b8636cad completed April 18, 2026, 3:30 a.m.
NER Named-entity recognition batch_69f60ac643108190ae81561267155791 completed May 2, 2026, 2:31 p.m.
PD Predicate disambiguation batch_69f602ce79ec8190b8336c2b9de18ac7 completed May 2, 2026, 1:57 p.m.
PDg Predicate description generation batch_69f606c15af88190958856a9e467b826 completed May 2, 2026, 2:14 p.m.
Created at: April 18, 2026, 4:46 a.m.