Triple
T28724525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Innere Neustadt (Dresden) |
E730184
|
entity |
| Predicate | hasCityQuarterStatusSince |
P30463
|
FINISHED |
| Object | 1991 |
—
|
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: 1991 | Statement: [Innere Neustadt (Dresden), hasCityQuarterStatusSince, 1991]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCityQuarterStatusSince Context triple: [Innere Neustadt (Dresden), hasCityQuarterStatusSince, 1991]
-
A.
hasCityQuarterStatus
Indicates that an entity holds the official status or designation of being a city quarter within a larger urban area.
-
B.
hasUrbanDistrictStatusSince
Indicates that an entity has held the legal or administrative status of an urban district continuously since a specified point in time.
-
C.
hasCityStatusFor
Indicates that an entity holds official city status within the jurisdiction or context of another entity.
-
D.
urbanStatusSince
chosen
Indicates the point in time since which an entity has held an urban status or classification.
-
E.
hasTownStatus
Indicates that an entity possesses the legal or administrative status of being recognized as a town.
- 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_69f043e91fe48190b73bcd8e08d433e0 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 28, 2026, 5:55 a.m.