Triple
T19700113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian Airborne Troops Day |
E473068
|
entity |
| Predicate | associatedWith |
P37
|
FINISHED |
| Object | VDV |
—
|
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: VDV | Statement: [Russian Airborne Troops Day, associatedWith, VDV]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: VDV Context triple: [Russian Airborne Troops Day, associatedWith, VDV]
-
A.
VDV
chosen
VDV is the elite airborne branch of Russia’s armed forces, known for rapid-deployment paratrooper and air-assault operations.
-
B.
VDV Day
VDV Day is an annual Russian holiday celebrating the country’s airborne troops with military demonstrations, ceremonies, and veteran gatherings.
-
C.
VDH
VDH is the state public health agency responsible for protecting and promoting the health of residents in Virginia.
-
D.
DVVD
DVVD is an architectural firm known for its role in the renovation of major public venues such as the Palais Omnisports de Paris-Bercy in Paris.
-
E.
VDP
VDP is a networking protocol used to automatically discover and configure virtual devices or ports in virtualized environments.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e642b4e01081908f857f219d5d7a24 |
completed | April 20, 2026, 3:13 p.m. |
Created at: April 10, 2026, 1:46 p.m.