Triple
T9935270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German-speaking Community of Belgium |
E192743
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | DG |
E192743
|
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 | Statement: [German-speaking Community of Belgium, shortName, DG]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: DG Context triple: [German-speaking Community of Belgium, shortName, DG]
-
A.
DG
chosen
DG is the abbreviation for the German-speaking Community, the small German-language region and federal community in eastern Belgium.
-
B.
DG
DG is the stock ticker symbol for Data General, a former American minicomputer manufacturer prominent in the 1970s and 1980s.
-
C.
GD
GD is the vehicle registration code used on license plates for cars registered in the city of Gdańsk, Poland.
-
D.
GD
GD is the abbreviation for Guangdong, a populous and economically significant coastal province in southern China.
-
E.
GD
GD is the stock ticker symbol for General Dynamics, a major American aerospace and defense corporation.
- 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_69ca82dd978c8190947124ab0d3315ac |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb5e263208190b6ea8b8b4e29805d |
completed | April 2, 2026, 12:18 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d228ddecfc8190850a098bf4074cc3 |
completed | April 5, 2026, 9:18 a.m. |
Created at: March 30, 2026, 8:44 p.m.