Triple
T24882261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zimri |
E622744
|
entity |
| Predicate | eventLeadingToDeath |
P54491
|
FINISHED |
| Object | siege of Tirzah by Omri |
—
|
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: siege of Tirzah by Omri | Statement: [Zimri, eventLeadingToDeath, siege of Tirzah by Omri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventLeadingToDeath Context triple: [Zimri, eventLeadingToDeath, siege of Tirzah by Omri]
-
A.
deathLeadsTo
Indicates that one entity’s death causes, results in, or brings about another event, state, or condition.
-
B.
deathDuringEvent
Indicates that an entity died while a specified event was occurring.
-
C.
notablePersonKilledThere
Indicates that a notable or famous person was killed at the referenced location.
-
D.
deathBy
chosen
Indicates a relationship where one entity’s death is caused by another entity, event, or factor.
-
E.
assassinationEvent
Indicates a deliberate killing of a specific individual, typically for political or strategic reasons, carried out as a planned 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_69e2fac4aa848190b3446a3922cec150 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:24 a.m.