Triple
T9230244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Detmold region |
E221796
|
entity |
| Predicate | hasRegionalPlanningFunction |
P12921
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Detmold region, hasRegionalPlanningFunction, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionalPlanningFunction Context triple: [Detmold region, hasRegionalPlanningFunction, yes]
-
A.
hasRegionalPlanningOrganization
Indicates that an entity is associated with or served by a specific regional planning organization responsible for coordinated planning activities in that area.
-
B.
hasRegionalRole
chosen
Indicates that an entity holds a specific role, function, or responsibility within a defined geographic region.
-
C.
hasRegionalDevelopmentBoard
Indicates that an entity is associated with or overseen by a specific regional development board.
-
D.
containsRegionalCouncil
Indicates that one administrative or geographic entity includes a regional council within its jurisdiction or boundaries.
-
E.
partOfPlanningRegion
Indicates that one entity is included within, or belongs to, a larger designated planning region.
- 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_69ca83ed628c8190bc02d641e57f097f |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccee17a2dc8190b373f78be7247f0d |
completed | April 1, 2026, 10:06 a.m. |
| PD | Predicate disambiguation | batch_69cc7a3daeb481908b0abde3fbc1f1f0 |
completed | April 1, 2026, 1:51 a.m. |
Created at: March 30, 2026, 7:29 p.m.