Triple
T10617033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hector International Airport |
E276146
|
entity |
| Predicate | FAAcode |
P420
|
FINISHED |
| Object | FAR |
E876081
|
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: FAR | Statement: [Hector International Airport, FAAcode, FAR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FAR Context triple: [Hector International Airport, FAAcode, FAR]
-
A.
FAR
FAR is the acronym for Cuba’s national military organization, the Revolutionary Armed Forces.
-
B.
FAR
FAR is the commonly used abbreviation for the Intergovernmental Panel on Climate Change’s First Assessment Report, a foundational scientific evaluation of climate change published in 1990.
-
C.
FAR
FAR is the station code for Faro railway station, a key rail transport hub serving the city of Faro in southern Portugal’s Algarve region.
-
D.
FAR
FAR is the acronym for Morocco's Royal Armed Forces, the country's unified military organization responsible for national defense.
-
E.
FAR
chosen
FAR is the IATA airport code for Hector International Airport serving Fargo, North Dakota.
- 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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d6df6e2df4819099a19b59d90d0dd1 |
completed | April 8, 2026, 11:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d97a2c8a048190b9a62f1c68ac217a |
completed | April 10, 2026, 10:31 p.m. |
Created at: April 8, 2026, 7:33 p.m.