Triple
T7002204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City Council of Lucerne |
E162361
|
entity |
| Predicate | hasDissolvedOrSeparatedFrom |
P73527
|
FINISHED |
| Object | none (still existing) |
—
|
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: none (still existing) | Statement: [City Council of Lucerne, hasDissolvedOrSeparatedFrom, none (still existing)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDissolvedOrSeparatedFrom Context triple: [City Council of Lucerne, hasDissolvedOrSeparatedFrom, none (still existing)]
-
A.
endedByDissolution
Indicates that a relationship, agreement, or entity was terminated specifically through a formal dissolution process.
-
B.
marriageEndedBy
Indicates that a marriage relationship between two entities has been terminated due to the action or decision of a specified party or event.
-
C.
dissolvedByMerger
Indicates that an entity ceased to exist as an independent entity because it was legally combined into another entity through a merger.
-
D.
wasDissolvedAfter
Indicates that one entity ceased to exist or operate at a later point in time than another entity’s dissolution.
-
E.
dividedFormerEntity
Indicates that an entity was once part of a single unified entity that has since been split into multiple separate entities.
- 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_69c68857ffc08190857dc62cd5253777 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dc1115c48190a9363473ae21b6c1 |
completed | March 27, 2026, 7:35 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c67c94819084fdcf0398606027 |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d8c575f081908b43d95d1d99b1a4 |
completed | March 27, 2026, 7:21 p.m. |
Created at: March 27, 2026, 2:33 p.m.