Triple

T27994752
Position Surface form Disambiguated ID Type / Status
Subject I-185 E706979 entity
Predicate formerPrimaryRouteTo P147208 FINISHED
Object Fort Benning 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: Fort Benning | Statement: [I-185, formerPrimaryRouteTo, Fort Benning]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: formerPrimaryRouteTo
Context triple: [I-185, formerPrimaryRouteTo, Fort Benning]
  • A. primaryRouteFrom
    Indicates that one entity serves as the main or preferred route originating from another entity.
  • B. primaryRouteOf chosen
    Indicates that one route is the main or most important pathway used for reaching or connecting to a particular destination or entity.
  • C. primaryRouteThrough
    Indicates that one location or path serves as the main or most significant route passing through another location or area.
  • D. originalRoute
    Indicates that one route is the initial or primary path from which another route is derived, modified, or compared.
  • E. formerRouteType
    Indicates that an entity previously had a specific route classification or type, which is no longer its current status.
  • 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_69ef96b980d88190a753b2f9a978595a completed April 27, 2026, 5:02 p.m.
NER Named-entity recognition batch_69fd76d1e5208190a6f26651492d1e3c completed May 8, 2026, 5:38 a.m.
PD Predicate disambiguation batch_69fd702a226c81908edfda00f4be4130 completed May 8, 2026, 5:10 a.m.
Created at: April 27, 2026, 7:52 p.m.