Triple
T15747503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NKVD |
E381757
|
entity |
| Predicate | followedBy |
P78
|
FINISHED |
| Object | MVD |
E57065
|
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: MVD | Statement: [NKVD, followedBy, MVD]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MVD Context triple: [NKVD, followedBy, MVD]
-
A.
MVD
chosen
The MVD was the Soviet Ministry of Internal Affairs, a powerful state security and police organ that, among other functions, administered the Gulag forced labor camp system.
-
B.
MVD
MVD is the IATA airport code for Carrasco International Airport, the main international gateway serving Montevideo, Uruguay.
-
C.
MDV
MDV is a venture capital firm known for investing in early-stage technology and life sciences companies.
-
D.
MDV
MDV is a regional public transport association and fare network serving Leipzig and the surrounding Central German area.
-
E.
MVRD
MVRD is the commonly used acronym for the regional government district that encompasses the metropolitan area of Vancouver in British Columbia, Canada.
- 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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0502d72008190b4d13a6b3a12e467 |
completed | April 16, 2026, 2:57 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff8309cba881909579ee5a62b3aa31 |
completed | May 9, 2026, 6:55 p.m. |
Created at: April 10, 2026, 4:46 a.m.