Triple
T38450295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VIB |
E912154
|
entity |
| Predicate | locatedInNUTS0Region |
P194905
|
FINISHED |
| Object | DE (Germany) |
—
|
LITERAL 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: DE (Germany) | Statement: [VIB, locatedInNUTS0Region, DE (Germany)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInNUTS0Region Context triple: [VIB, locatedInNUTS0Region, DE (Germany)]
-
A.
locatedInNUTS2
Indicates that one entity is geographically situated within, or belongs to, a specific NUTS-2 (Nomenclature of Territorial Units for Statistics level 2) region.
-
B.
hasNUTS0Country
chosen
Indicates that an entity is associated with, or belongs to, a specific country at the NUTS level 0 (national) in the NUTS classification system.
-
C.
NUTSRegionCode
Indicates the classification of an entity according to the NUTS (Nomenclature of Territorial Units for Statistics) regional coding system used for statistical regions.
-
D.
locatedInEurozone
Indicates that the subject entity is situated within the geographic or economic area of the Eurozone.
-
E.
locatedInNorthernEurope
Indicates that the subject is geographically situated within the region of Northern Europe.
- F. None of above.
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_69f76e84e2dc81908badf05b3aafa9ea |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.