Triple
T13956489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 13/31 |
E335676
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | LaGrange, Georgia |
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, Georgia | Statement: [Runway 13/31, locatedIn, LaGrange, Georgia]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LaGrange, Georgia Context triple: [Runway 13/31, locatedIn, LaGrange, Georgia]
-
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.
Oglethorpe, Georgia
Oglethorpe, Georgia is a small city in central Georgia that serves as the administrative and commercial hub of Macon County.
-
E.
Calhoun, Georgia
Calhoun, Georgia is a small city in northwest Georgia known as the county seat of Gordon County and a regional hub along Interstate 75.
- 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_69d81c61f3508190aaf2ca0dc0002c59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e78a4a481908e438745631a43c0 |
completed | April 14, 2026, 12:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fba1d27a0c8190b5d95ea86fc1a420 |
completed | May 6, 2026, 8:17 p.m. |
Created at: April 9, 2026, 10:17 p.m.