Triple
T9240505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FV |
E222045
|
entity |
| Predicate | airlineCallsign |
P13478
|
FINISHED |
| Object | ROSSIYA |
E252549
|
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: ROSSIYA | Statement: [FV, airlineCallsign, ROSSIYA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ROSSIYA Context triple: [FV, airlineCallsign, ROSSIYA]
-
A.
ROSSIYA
chosen
ROSSIYA is the radio callsign used by Rossiya Airlines, a major Russian carrier based in Saint Petersburg.
-
B.
Russia
Russia is the world’s largest country by land area, spanning Eastern Europe and northern Asia and exerting major political, military, and cultural influence globally.
-
C.
Rusko
Rusko is a small municipality in southwestern Finland known for its rural character and proximity to the city of Turku.
-
D.
Rus'
Rus' was a medieval East Slavic state that emerged in Eastern Europe and laid the foundations for the later Russian, Ukrainian, and Belarusian nations.
-
E.
Rusa
Rusa is a genus of deer native to South and Southeast Asia, including species such as the Javan rusa and sambar.
- 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_69ca83ee26cc81909ac624e190597d6d |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccf0a3888c8190b72d8d0b850bdfbc |
completed | April 1, 2026, 10:17 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d100b8f80c8190bef93de787227a51 |
completed | April 4, 2026, 12:14 p.m. |
Created at: March 30, 2026, 7:30 p.m.