Triple
T11097296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DG MOVE |
E262408
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | DG MOVE |
E262408
|
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: DG MOVE | Statement: [DG MOVE, shortName, DG MOVE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: DG MOVE Context triple: [DG MOVE, shortName, DG MOVE]
-
A.
DG MOVE
chosen
DG MOVE is the European Commission department responsible for developing and implementing EU policies on transport and mobility across all modes.
-
B.
DG JUST
DG JUST is the European Commission department responsible for EU policies on justice, consumer protection, and equality.
-
C.
DG
DG is the abbreviation for the German-speaking Community, the small German-language region and federal community in eastern Belgium.
-
D.
DG
DG is the stock ticker symbol for Data General, a former American minicomputer manufacturer prominent in the 1970s and 1980s.
-
E.
DG I
DG I is the Council of Europe’s Directorate General responsible for promoting and protecting human rights and the rule of law across member states.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79a0a02cc8190a15df663d4860163 |
completed | April 9, 2026, 12:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e42d69c8b4819092614e83e855430e |
completed | April 19, 2026, 1:18 a.m. |
Created at: April 8, 2026, 9:27 p.m.