Triple
T33039497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Möderscheid |
E845418
|
entity |
| Predicate | hasLocalCouncilRepresentation |
P196635
|
FINISHED |
| Object | Amel municipal council |
—
|
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: Amel municipal council | Statement: [Möderscheid, hasLocalCouncilRepresentation, Amel municipal council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalCouncilRepresentation Context triple: [Möderscheid, hasLocalCouncilRepresentation, Amel municipal council]
-
A.
isRepresentedInCityCouncilBy
Indicates that a person or group has a designated representative who serves on the city council on their behalf.
-
B.
hasCouncilSeat
Indicates that an entity holds a position or seat on a governing council.
-
C.
isPartOfDistrictRepresentation
Indicates that one entity serves as a component or segment within the overall representation of a specific district.
-
D.
hasCouncilDistrict
Indicates that an entity is located within or represented by a specific council district.
-
E.
councilRepresentation
Indicates that one entity serves as an official representative or delegate for another entity within a council or governing body.
- 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_69f34951348c8190b56746b0a7018182 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe5ec9028081909ae3d6fbe2f4cbbc |
completed | May 8, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69fe5e1d715881909fc516fafc707644 |
completed | May 8, 2026, 10:05 p.m. |
| PDg | Predicate description generation | batch_69fe5ec84910819094cb15269ace7c51 |
completed | May 8, 2026, 10:08 p.m. |
Created at: May 1, 2026, 1:24 a.m.