Triple
T3135170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santa Fe Regional Airport |
E65509
|
entity |
| Predicate | FAAcode |
P420
|
FINISHED |
| Object | SAF |
E328858
|
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: SAF | Statement: [Santa Fe Regional Airport, FAAcode, SAF]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SAF Context triple: [Santa Fe Regional Airport, FAAcode, SAF]
-
A.
SAF
chosen
SAF is the three-letter IATA airport code for Santa Fe Regional Airport in Santa Fe, New Mexico.
-
B.
SAU
SAU is an international university established by the South Asian Association for Regional Cooperation (SAARC) in New Delhi, India, focusing on postgraduate and doctoral education and research for students from South Asian countries.
-
C.
SAU
SAU is the three-letter ISO 3166-1 alpha-3 country code assigned to Saudi Arabia.
-
D.
KSAF
KSAF is the ICAO airport code for Santa Fe Regional Airport, a public airport serving Santa Fe, New Mexico.
-
E.
SA3
SA3 is the 3GPP security working group responsible for specifying and evolving security architecture and mechanisms across mobile communication standards.
- 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_69ad8581c25c8190b0d85ba9b9baa531 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada5637de0819089393429c4017298 |
completed | March 8, 2026, 4:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b224dcd1bc8190948b80c686d0e641 |
completed | March 12, 2026, 2:28 a.m. |
Created at: March 8, 2026, 3:05 p.m.