Triple
T9738078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Wings Airlines |
E236115
|
entity |
| Predicate | ICAOcode |
P419
|
FINISHED |
| Object | RWZ |
E235074
|
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: RWZ | Statement: [Red Wings Airlines, ICAOcode, RWZ]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RWZ Context triple: [Red Wings Airlines, ICAOcode, RWZ]
-
A.
RWZ
chosen
RWZ is the ICAO airline designator assigned to Red Wings Airlines, a Russian passenger carrier.
-
B.
RZ
RZ is the vehicle registration code used on license plates for the district of Lauenburg in the German state of Schleswig-Holstein.
-
C.
ZWZ
ZWZ was the Polish underground military organization formed during World War II that later evolved into the Home Army (Armia Krajowa), the main resistance force against Nazi occupation.
-
D.
WZ
WZ is the IATA airline designator assigned to Red Wings Airlines, a Russian passenger carrier.
-
E.
ŻW
ŻW is the abbreviated name of Poland’s Military Gendarmerie, the armed forces’ military police force responsible for law enforcement and security within the Polish military.
- 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_69ca84d313e88190983ee6ffd0ef60d2 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9ef2ba048190811d6f4251fdb270 |
completed | April 1, 2026, 10:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1afd74a308190ae1a618bab5f7841 |
completed | April 5, 2026, 12:41 a.m. |
Created at: March 30, 2026, 8:22 p.m.