Triple
T3840802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ernestine branch of the House of Wettin |
E93443
|
entity |
| Predicate | splitEvent |
P33767
|
FINISHED |
| Object | Division of the Wettin lands |
—
|
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: Division of the Wettin lands | Statement: [Ernestine branch of the House of Wettin, splitEvent, Division of the Wettin lands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: splitEvent Context triple: [Ernestine branch of the House of Wettin, splitEvent, Division of the Wettin lands]
-
A.
spinOff
Indicates that a new entity is created by separating or divesting part of an existing entity, forming an independent offshoot derived from the original.
-
B.
separatedInto
Indicates that something has been divided or split into distinct parts, groups, or components.
-
C.
parallelEvent
Indicates that two or more events occur at the same time or overlap in time without a required order between them.
-
D.
reasonForSplit
Indicates the cause, motivation, or circumstance that led to a separation or breakup between entities.
-
E.
divisionOccurred
chosen
Indicates that one entity has been separated into two or more distinct parts or groups through a division event.
- 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_69aed96ce578819084ab16e3439976c9 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeebb235088190b115623e54ea2ab1 |
completed | March 9, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69aee74dcecc819098285483ec721b40 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:18 p.m.