Triple
T28928534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lützel |
E733717
|
entity |
| Predicate | hasMunicipalKeyRole |
P81461
|
FINISHED |
| Object | Stadtteil nördlich der Mosel |
—
|
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: Stadtteil nördlich der Mosel | Statement: [Lützel, hasMunicipalKeyRole, Stadtteil nördlich der Mosel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMunicipalKeyRole Context triple: [Lützel, hasMunicipalKeyRole, Stadtteil nördlich der Mosel]
-
A.
hasMunicipalSeatFunction
Indicates that an entity serves as the administrative or municipal seat (central governing location) for a municipality.
-
B.
isMunicipal
Indicates that something belongs to, is administered by, or is characteristic of a municipality or local city government.
-
C.
municipalKey
Indicates a unique identifier that links an entity to a specific municipality within an administrative or geographic system.
-
D.
hasLocalGovernanceRole
chosen
Indicates that an entity holds an official position or responsibility within a local or municipal governing body.
-
E.
hasMunicipalGovernment
Indicates that an entity is administered or governed by a municipal-level governmental authority.
- 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_69f05b0b49b08190b8994b339c7980f6 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 28, 2026, 8:25 a.m.