Triple
T11955521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet state security organs |
E284541
|
entity |
| Predicate | hasComponent |
P35
|
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: [Soviet state security organs, hasComponent, MVD]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MVD Context triple: [Soviet state security organs, hasComponent, 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.
MDV
MDV is a venture capital firm known for investing in early-stage technology and life sciences companies.
-
C.
MDV
MDV is a regional public transport association and fare network serving Leipzig and the surrounding Central German area.
-
D.
MVRD
MVRD is the commonly used acronym for the regional government district that encompasses the metropolitan area of Vancouver in British Columbia, Canada.
-
E.
MVE
MVE is the station code for Mount Vernon East, a Metro-North Railroad commuter rail station in Mount Vernon, New York.
- 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d90366fda8819083168c93abad27d4 |
completed | April 10, 2026, 2:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f459175f808190974ac70431f35c74 |
completed | May 1, 2026, 7:41 a.m. |
Created at: April 8, 2026, 9:45 p.m.