Triple
T2437133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EVA Air |
E52986
|
entity |
| Predicate | callsign |
P1565
|
FINISHED |
| Object | EVA |
E265985
|
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: EVA | Statement: [EVA Air, callsign, EVA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: EVA Context triple: [EVA Air, callsign, EVA]
-
A.
EVA
chosen
EVA is the ICAO airline designator for EVA Air, a major Taiwanese international carrier based in Taoyuan.
-
B.
Eva
Eva is a feminine given name of Hebrew origin, equivalent to "Eve" and widely used in many languages and cultures.
-
C.
EGVA
EGVA is the ICAO airport code for RAF Fairford, a Royal Air Force station in Gloucestershire, England used primarily by the United States Air Force for bomber and airlift operations.
-
D.
Egvekinot
Egvekinot is a remote urban-type settlement and port on the coast of the Bering Sea in Russia’s Far East, serving as an important local center in the Chukotka region.
-
E.
Electryon
Electryon is a king of Mycenae in Greek mythology, known primarily as the grandfather of the hero Heracles.
- 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_69ab4959bcc0819083246f9fb10439e3 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abc9f342e88190a430b02842ded418 |
completed | March 7, 2026, 6:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69aef0ad31b8819084813b65b46bc9fc |
completed | March 9, 2026, 4:09 p.m. |
Created at: March 6, 2026, 9:43 p.m.