Triple
T2923519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Endeavor Air |
E78787
|
entity |
| Predicate | IATACode |
P418
|
FINISHED |
| Object | 9E |
E78787
|
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: 9E | Statement: [Endeavor Air, IATACode, 9E]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 9E Context triple: [Endeavor Air, IATACode, 9E]
-
A.
9E
chosen
9E is the IATA airline designator used by Endeavor Air, a regional carrier operating flights primarily for Delta Air Lines in North America.
-
B.
9D
9D is the designation for a state highway in New York known as New York State Route 9D.
-
C.
9N
9N is the designation for a New York State highway that runs along portions of the Hudson River and Lake George, serving communities in the eastern part of the state.
-
D.
9X
9X is the IATA airline designator assigned to Southern Airways Express, a U.S.-based regional commuter airline.
-
E.
9W
9W is a U.S. highway designation used for a north–south route running primarily through New York and New Jersey along the west side of the Hudson River.
- 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_69ad8b0c2ad081909ff87050ae542bb9 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad97bf2df88190bd4f1e90d4656507 |
completed | March 8, 2026, 3:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b056375b5c819081c7d4fd506cbf25 |
completed | March 10, 2026, 5:34 p.m. |
Created at: March 8, 2026, 2:55 p.m.