Triple
T24351466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duttweiler |
E613800
|
entity |
| Predicate | belongsToDistrictLevelCity |
P155896
|
FINISHED |
| Object | Neustadt an der Weinstraße |
—
|
NE NERFINISHED |
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: Neustadt an der Weinstraße | Statement: [Duttweiler, belongsToDistrictLevelCity, Neustadt an der Weinstraße]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToDistrictLevelCity Context triple: [Duttweiler, belongsToDistrictLevelCity, Neustadt an der Weinstraße]
-
A.
cityDistrictLevel
Indicates that one administrative unit is a district-level subdivision within a given city in the territorial hierarchy.
-
B.
containsDistrictMunicipality
Indicates that an administrative region includes one or more district municipalities within its boundaries.
-
C.
belongsToDistrictBeforeCityStatus
Indicates that an entity was part of a specific district prior to the area being granted city status.
-
D.
hasCityDistrictAlong
Indicates that a city district is located along or adjacent to a specified linear feature, such as a road, river, or coastline.
-
E.
inCityDistrict
Indicates that one entity is located within the boundaries of a specific city district.
- 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_69e2d7ddd29481909e7f539a6072bd71 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293457120819098af138fdd01846d |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 1:59 a.m.