Triple
T616901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quakenbrück |
E14423
|
entity |
| Predicate | hasRegionCodeNUTS |
P2415
|
FINISHED |
| Object | DE94C |
—
|
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: DE94C | Statement: [Quakenbrück, hasRegionCodeNUTS, DE94C]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionCodeNUTS Context triple: [Quakenbrück, hasRegionCodeNUTS, DE94C]
-
A.
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.
-
B.
hasRegionCode
Indicates that an entity is associated with a specific regional identifier or code.
-
C.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
D.
hasPostalAddressRegion
Indicates the region component (such as state, province, or area) associated with an entity’s postal address.
-
E.
isUNGeoschemeRegion
Indicates that a region is classified according to the United Nations geoscheme regional grouping system.
- 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_69a4934b17c881909ace8270e8ddd202 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e22f3688190a512bec3f0347814 |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49cfd15288190b4abdbd0bce3edcd |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.