Triple
T35609309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeuss |
E1028987
|
entity |
| Predicate | partOfAfterMerger |
P38393
|
FINISHED |
| Object | municipality of Murten |
—
|
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: municipality of Murten | Statement: [Jeuss, partOfAfterMerger, municipality of Murten]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfAfterMerger Context triple: [Jeuss, partOfAfterMerger, municipality of Murten]
-
A.
affiliationAfterMerger
Indicates that an entity becomes affiliated with another entity as a result of a merger that occurs after a specified point in time.
-
B.
partOfAfter
chosen
Indicates that one entity becomes a component or subset of another entity at some point after a specified time or event.
-
C.
mergerPartner
Indicates that two entities are involved as counterparties in a merger transaction with each other.
-
D.
partOfBeforeDissolution
Indicates that one entity was a component or subdivision of another entity during a period prior to the latter’s dissolution.
-
E.
demergedInto
Indicates that an entity has been split or separated into one or more distinct successor entities as a result of a demerger process.
- 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_69f76e0653ec81909b1b813c126c6574 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a008ebb22408190a2293bced40a7e53 |
completed | May 10, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_6a008e8715dc8190ab23292605901bf4 |
completed | May 10, 2026, 1:56 p.m. |
Created at: May 3, 2026, 4:05 p.m.