Triple

T6691800
Position Surface form Disambiguated ID Type / Status
Subject Hickory Regional Airport E152644 entity
Predicate locatedIn P40 FINISHED
Object Hickory E27483 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: Hickory | Statement: [Hickory Regional Airport, locatedIn, Hickory]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hickory
Context triple: [Hickory Regional Airport, locatedIn, Hickory]
  • A. Hickory, North Carolina chosen
    Hickory, North Carolina is a mid-sized city in the western Piedmont region known historically for its furniture manufacturing and diversified manufacturing economy.
  • B. Woodfin
    Woodfin is the surname of Randall Woodfin, an American politician and mayor of Birmingham, Alabama.
  • C. Greenwood
    Greenwood is a residential neighborhood within the city of Wakefield in Middlesex County, Massachusetts.
  • D. Greenwood
    Greenwood is a common English surname borne by numerous notable individuals across fields such as music, sports, and politics.
  • E. Greenwood
    Greenwood is a residential neighborhood within the town of Bicester in Oxfordshire, England.
  • 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_69c6880687b08190805278b504d1c92c completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6b193a8c08190a99152a8eca018e6 completed March 27, 2026, 4:34 p.m.
NED1 Entity disambiguation (via context triple) batch_69c70af2ede08190821fd599a3bfc879 completed March 27, 2026, 10:55 p.m.
Created at: March 27, 2026, 2:05 p.m.