Triple
T11051335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airbus Transport International |
E261259
|
entity |
| Predicate | callsign |
P1565
|
FINISHED |
| Object | BELUGA |
E204398
|
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: BELUGA | Statement: [Airbus Transport International, callsign, BELUGA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BELUGA Context triple: [Airbus Transport International, callsign, BELUGA]
-
A.
Beluga
chosen
The Beluga is a large, bulbous-headed cargo aircraft developed by Airbus, known for transporting oversized aerospace components.
-
B.
Baikal seal
The Baikal seal is a small, uniquely freshwater species of earless seal endemic to Russia’s Lake Baikal and adapted to its cold, deep waters.
-
C.
Caspian seal
The Caspian seal is a small, endangered earless seal species found exclusively in the landlocked Caspian Sea region.
-
D.
Dolphin
Dolphin was the internal codename used by Nintendo during the development of the GameCube console.
-
E.
Dolphin
Dolphin is a lightweight, user-friendly file manager for the KDE Plasma desktop environment, offering advanced navigation and file organization features.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d798698bd88190aa97afd37f55e19f |
completed | April 9, 2026, 12:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e3aa146b148190a87205e542cc718f |
completed | April 18, 2026, 3:58 p.m. |
Created at: April 8, 2026, 9:26 p.m.