Triple
T22040697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rossiya Special Flight Detachment |
E544629
|
entity |
| Predicate | IATACode |
P418
|
FINISHED |
| Object | RSD |
—
|
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: RSD | Statement: [Rossiya Special Flight Detachment, IATACode, RSD]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RSD Context triple: [Rossiya Special Flight Detachment, IATACode, RSD]
-
A.
RSD
RSD is the official currency code for the Serbian dinar, the legal tender of Serbia.
-
B.
RSD
The RSD was the Reich Security Service, an elite Nazi protective unit responsible for the personal security of Adolf Hitler and other top Third Reich leaders.
-
C.
RSD
chosen
RSD is the IATA airport code for Rock Sound International Airport in the Bahamas.
-
D.
Rsd
Rsd is the official station code used to identify Roosendaal railway station in the Netherlands.
-
E.
RSP
RSP is the commonly used abbreviation for the United Nations Environment Programme’s Regional Seas Programme, a global initiative aimed at protecting and managing the marine and coastal environment through regional cooperation.
- 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_69e11e32445c8190ab97089b48a130bb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12828fc788190a22c0e9c2372656b |
completed | April 28, 2026, 9:35 p.m. |
Created at: April 16, 2026, 8:25 p.m.