Triple
T19514669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Innere Stadt |
E488246
|
entity |
| Predicate | isDistrictNumber |
P47247
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Innere Stadt, isDistrictNumber, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDistrictNumber Context triple: [Innere Stadt, isDistrictNumber, 1]
-
A.
hasMunicipalDistrictNumber
chosen
Indicates that a municipality or local administrative unit is assigned a specific district number within its municipal structure.
-
B.
communityDistrictNumber
Indicates the specific community district identifier associated with an entity or location.
-
C.
isSingleDistrictFor
Indicates that one district uniquely and exclusively serves or applies to a given entity, with no other districts sharing that role.
-
D.
isInnerDistrictOf
Indicates that one district is geographically or administratively located within and subordinate to another, larger district.
-
E.
includesDistrict
Indicates that one administrative or geographic entity contains or encompasses a specific district within its boundaries.
- 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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6359a7070819099d925447c80bf23 |
completed | April 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7bd25881908caa04eaef1f6718 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:40 p.m.