Triple
T10746326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vystavochny Tsentr |
E253457
|
entity |
| Predicate | serves |
P98
|
FINISHED |
| Object | VDNKh |
E773225
|
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: VDNKh | Statement: [Vystavochny Tsentr, serves, VDNKh]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: VDNKh Context triple: [Vystavochny Tsentr, serves, VDNKh]
-
A.
VDNKh
chosen
VDNKh is a vast exhibition and amusement complex in Moscow known for its grand Soviet-era pavilions, monuments, and cultural attractions.
-
B.
VRN
VRN is the public transport association serving Germany’s Rhine-Neckar metropolitan region, coordinating regional and local transit services across multiple states.
-
C.
Vdm
Vdm is the official station code for Van der Madeweg, a metro station in Amsterdam, Netherlands.
-
D.
VDY
VDY is the IATA airport code for Jindal Vijaynagar Airport in Karnataka, India.
-
E.
VDV
VDV is the elite airborne branch of Russia’s armed forces, known for rapid-deployment paratrooper and air-assault operations.
- 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d711b85d9c8190a66f536e2f22ed04 |
completed | April 9, 2026, 2:40 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69de230b461c81909a98085079676b95 |
completed | April 14, 2026, 11:20 a.m. |
Created at: April 8, 2026, 9:15 p.m.