Triple
T17678077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Tepual International Airport |
E440688
|
entity |
| Predicate | timeZone |
P109
|
FINISHED |
| Object | CLT |
E1074358
|
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: CLT | Statement: [El Tepual International Airport, timeZone, CLT]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CLT Context triple: [El Tepual International Airport, timeZone, CLT]
-
A.
CLT
CLT is the IATA airport code for Charlotte Douglas International Airport, a major airline hub in Charlotte, North Carolina.
-
B.
CLT
CLT is a fundamental statistical principle stating that the sum or average of many independent, identically distributed random variables tends to follow a normal distribution, regardless of the original distribution.
-
C.
CLT
CLT is the National Rail station code for Clacton-on-Sea railway station in Essex, England.
-
D.
CLT
chosen
CLT is the standard time zone used in Chile, typically corresponding to UTC−4 hours.
-
E.
CLT
CLT is the station code for Kozhikode railway station, a major rail hub in the Indian state of Kerala.
- 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46f6e959c819092d9d33e79bd51f7 |
completed | April 19, 2026, 6 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a022325d6108190975082abcdb21ce1 |
completed | May 11, 2026, 6:42 p.m. |
Created at: April 10, 2026, 10:01 a.m.