Triple
T7766023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rheinbach |
E176146
|
entity |
| Predicate | hasDistrictKey |
P78224
|
FINISHED |
| Object | 05382 |
—
|
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: 05382 | Statement: [Rheinbach, hasDistrictKey, 05382]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDistrictKey Context triple: [Rheinbach, hasDistrictKey, 05382]
-
A.
containsDistrictMunicipality
Indicates that an administrative region includes one or more district municipalities within its boundaries.
-
B.
hasCurrentDistrict
Indicates that an entity is currently located in, represented by, or associated with a specific administrative or electoral district.
-
C.
includesDistrict
Indicates that one administrative or geographic entity contains or encompasses a specific district within its boundaries.
-
D.
isSingleDistrictFor
Indicates that one district uniquely and exclusively serves or applies to a given entity, with no other districts sharing that role.
-
E.
hasJudicialDistrict
Indicates that an entity falls within or is associated with a specific judicial district for legal or court-related purposes.
- 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_69c69962923c8190ac74d28b4f9fe0a0 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7043279748190b30882e9cc6cca54 |
completed | March 27, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69c7016f4ce881909c2e9f610255187b |
completed | March 27, 2026, 10:15 p.m. |
| PDg | Predicate description generation | batch_69c702a78edc819090c3448d33c8c381 |
completed | March 27, 2026, 10:20 p.m. |
Created at: March 27, 2026, 4:09 p.m.