Triple
T7106618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Texas Regional Airport |
E165602
|
entity |
| Predicate | FAAIdentifier |
P420
|
FINISHED |
| Object | GYI |
E165603
|
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: GYI | Statement: [North Texas Regional Airport, FAAIdentifier, GYI]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: GYI Context triple: [North Texas Regional Airport, FAAIdentifier, GYI]
-
A.
GYI
chosen
GYI is the FAA location identifier for North Texas Regional Airport, a public airport serving the Sherman–Denison area in Texas.
-
B.
GYD
GYD is the official currency code for the Guyanese dollar, the national currency of Guyana.
-
C.
GYY
GYY is the IATA airport code for Gary/Chicago International Airport, a regional airport serving the Gary, Indiana and greater Chicago metropolitan area.
-
D.
GHY
GHY is the station code for Guwahati Junction, a major railway hub in the northeastern Indian state of Assam.
-
E.
KGYI
KGYI is the ICAO airport code for North Texas Regional Airport, a public airport serving the Sherman–Denison area in Texas, United States.
- 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_69c6888120f081908f8f01b201dc4a4c |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e5b9f13c8190a14898f241ec17a4 |
completed | March 27, 2026, 8:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7ad83aa288190b06262ac9898f5c1 |
completed | March 28, 2026, 10:29 a.m. |
Created at: March 27, 2026, 2:42 p.m.