Triple
T9539864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ibex Airlines |
E230121
|
entity |
| Predicate | IATACode |
P418
|
FINISHED |
| Object | FW |
E230121
|
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: FW | Statement: [Ibex Airlines, IATACode, FW]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FW Context triple: [Ibex Airlines, IATACode, FW]
-
A.
FW
FW refers to the Free Voters (Freie Wähler), a German political association and party known for its strong local-government focus and presence in Bavarian municipal and regional politics.
-
B.
FW
chosen
FW is the IATA airline designator assigned to the Japanese regional carrier Ibex Airlines.
-
C.
WF
WF is the common abbreviation for Windows Workflow Foundation, a Microsoft technology for building workflow-enabled applications within the .NET framework.
-
D.
WF
WF is the common abbreviation for Wikifunctions, a Wikimedia project aimed at creating a collaborative catalog of reusable functions.
-
E.
FWN
FWN is the standard abbreviation used for the Fort Wayne TinCaps, a Minor League Baseball team based in Fort Wayne, Indiana.
- 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_69ca847b1b3081908f72bc932c17cc41 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd98e4df6c8190a4d1160c42daa45f |
completed | April 1, 2026, 10:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d14c5da5a081909d646c69d5de8e18 |
completed | April 4, 2026, 5:37 p.m. |
Created at: March 30, 2026, 8:01 p.m.