Triple
T21234587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sfax–Thyna International Airport |
E523309
|
entity |
| Predicate | IATACode |
P418
|
FINISHED |
| Object | SFA |
—
|
NE NERFINISHED |
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: SFA | Statement: [Sfax–Thyna International Airport, IATACode, SFA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SFA Context triple: [Sfax–Thyna International Airport, IATACode, SFA]
-
A.
SFA
The SFA is the Scottish Football Association, the main governing body for football in Scotland.
-
B.
SFA
chosen
SFA is the IATA airport code for Sfax–Thyna International Airport serving the city of Sfax in Tunisia.
-
C.
SFA
SFA is a public university in Nacogdoches, Texas, known for its academic programs, research, and Lumberjacks athletic teams.
-
D.
SFA
SFA is the National Rail station code for Stratford International railway station in London, England.
-
E.
SFA
SFA is the abbreviation for the Swiss Federal Archives, the national institution responsible for preserving and providing access to the official records of the Swiss Confederation.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b512ad94819087942b2ed925185f |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7351e4b908190bc02f063e3822123 |
completed | April 21, 2026, 8:28 a.m. |
Created at: April 16, 2026, 3:46 p.m.