Triple
T25914750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regierungsbezirk Kassel |
E653000
|
entity |
| Predicate | hasRegionKey |
P192420
|
FINISHED |
| Object | 06 |
—
|
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: 06 | Statement: [Regierungsbezirk Kassel, hasRegionKey, 06]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionKey Context triple: [Regierungsbezirk Kassel, hasRegionKey, 06]
-
A.
isKeyRegionFor
Indicates that one region plays a central or strategically important role in relation to a specified process, function, or larger area.
-
B.
isKeyRegionIn
Indicates that a region plays a central or strategically important role within a larger area, system, or context.
-
C.
hasRegionFunction
Indicates that a region is associated with a particular function, role, or operational purpose.
-
D.
hasRegionProperty
Indicates that a region is associated with a specific property or characteristic.
-
E.
hasDistrictKey
Indicates that an entity is associated with a specific district through a unique identifying key.
- F. None of above. chosen
Provenance (4 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_69e7ab3e025c819086771607157f0015 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
| PDg | Predicate description generation | batch_69fd0b92150881909b1166fe6d09aa19 |
completed | May 7, 2026, 10 p.m. |
Created at: April 22, 2026, 8:30 a.m.