Triple
T36353372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RE |
E895269
|
entity |
| Predicate | associatedGovernmentDistrict |
P128478
|
FINISHED |
| Object | Münster region |
—
|
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: Münster region | Statement: [RE, associatedGovernmentDistrict, Münster region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedGovernmentDistrict Context triple: [RE, associatedGovernmentDistrict, Münster region]
-
A.
governmentalDistrictOf
chosen
Indicates that a governmental district is the administrative district to which a given entity belongs or in which it is located.
-
B.
governmentDistrict
Indicates that a government entity has jurisdiction over or is administratively associated with a specific district.
-
C.
servesGovernmentDistrict
Indicates that an entity provides official services or representation to a specific government district.
-
D.
locatedNearGovernmentDistrict
Indicates that one entity is situated close to or in the immediate vicinity of a government district.
-
E.
sourceDistrict
Indicates the district from which something originates, is sent, or is sourced.
- 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_69f76e4f437c8190a1af3ea2564f41f5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.