Triple

T10755840
Position Surface form Disambiguated ID Type / Status
Subject LaGrange–Callaway Airport E253690 entity
Predicate cityServed P82 FINISHED
Object LaGrange E30624 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: LaGrange | Statement: [LaGrange–Callaway Airport, cityServed, LaGrange]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: LaGrange
Context triple: [LaGrange–Callaway Airport, cityServed, LaGrange]
  • A. LaGrange
    LaGrange is a town in Dutchess County, New York, known as a suburban community in the Hudson Valley region.
  • B. LaGrange chosen
    LaGrange is a small city in western Georgia known for its historic downtown, proximity to West Point Lake, and role as an economic and cultural center for the surrounding region.
  • C. LaGrange
    LaGrange is a small village in northeastern Ohio, United States, known for its residential community and local parks.
  • D. Aiken
    Aiken is a variant spelling of the surname Aitken, which is of Scottish origin.
  • E. Macon
    Macon is a surname of English and French origin borne by various notable individuals, including American statesman Nathaniel Macon.
  • 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_69d6aa5f54f4819082d0bbcb6f8797e6 completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d72e9e224c819099d16aba77322812 completed April 9, 2026, 4:44 a.m.
NED1 Entity disambiguation (via context triple) batch_69de84a63de0819085f1e982c8348811 completed April 14, 2026, 6:17 p.m.
Created at: April 8, 2026, 9:15 p.m.