Triple
T25017370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boleslaus I the Cruel |
E626175
|
entity |
| Predicate | causeOfBrotherDeath |
P144
|
FINISHED |
| Object | assassination of Saint Wenceslaus at Stará Boleslav |
—
|
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: assassination of Saint Wenceslaus at Stará Boleslav | Statement: [Boleslaus I the Cruel, causeOfBrotherDeath, assassination of Saint Wenceslaus at Stará Boleslav]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfBrotherDeath Context triple: [Boleslaus I the Cruel, causeOfBrotherDeath, assassination of Saint Wenceslaus at Stará Boleslav]
-
A.
causeOfHusbandDeath
Indicates that the subject is the cause or reason for the husband’s death.
-
B.
brothersKilledBy
Indicates that the referenced individuals are brothers who were killed by the same agent or in the same event.
-
C.
reasonForDeath
Indicates the cause, circumstance, or condition that led to an entity’s death.
-
D.
causeOfDeath
chosen
Indicates the specific factor, event, or condition that directly resulted in an entity’s death.
-
E.
deathCharacteristic
Indicates a characteristic, attribute, or quality specifically associated with a death event or the manner in which death occurred.
- 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_69e2ff27755881908490178e83701160 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:06 a.m.