Triple
T6578917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian Air Force |
E157241
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | VVS |
E63696
|
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: VVS | Statement: [Russian Air Force, abbreviation, VVS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: VVS Context triple: [Russian Air Force, abbreviation, VVS]
-
A.
VVS
chosen
VVS was the air force branch of the Soviet Union’s armed forces, responsible for military aviation and air defense operations.
-
B.
BVVS
BVVS is the commonly used Bulgarian abbreviation for the Bulgarian Air Force, the aerial warfare branch of Bulgaria’s armed forces.
-
C.
VV
VV is the common abbreviation for VistaVision, a high-resolution widescreen 35mm motion picture film format developed by Paramount Pictures in the 1950s.
-
D.
VIV
VIV is the ICAO airline designator assigned to Viva Aerobus, a Mexican low-cost carrier.
-
E.
VSI
VSI is the commonly used abbreviation for the "Very Short Introductions" series of concise, authoritative books published by Oxford University Press on a wide range of subjects.
- 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_69c6882b3a108190b3a9eb343ae4162c |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ae8dad608190b4708368a7af6e5d |
completed | March 27, 2026, 4:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6d56fe8f08190ad30773f29b207c5 |
completed | March 27, 2026, 7:07 p.m. |
Created at: March 27, 2026, 1:54 p.m.