Triple
T35380436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roßdorf |
E1022626
|
entity |
| Predicate | hasEuropeanNUTSLevel1Region |
P2415
|
FINISHED |
| Object | DE |
—
|
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 | Statement: [Roßdorf, hasEuropeanNUTSLevel1Region, DE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEuropeanNUTSLevel1Region Context triple: [Roßdorf, hasEuropeanNUTSLevel1Region, DE]
-
A.
belongsToEURegionType
Indicates that an entity is classified within a specific type or category of European Union region.
-
B.
NUTSRegionCode
chosen
Indicates the classification of an entity according to the NUTS (Nomenclature of Territorial Units for Statistics) regional coding system used for statistical regions.
-
C.
europeanUnionRegion
Indicates that an entity is located in, associated with, or falls under the jurisdiction of a region defined by or within the European Union.
-
D.
isInEuropeanUnionCountry
Indicates that the subject entity is located within, or belongs to, a country that is a member of the European Union.
-
E.
europeanRegion
Indicates that an entity is located in, associated with, or classified as part of a region within 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_69f76df28d8c819089f2c5799fe7d079 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.