Triple
T26218933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Ain Jalood |
E655709
|
entity |
| Predicate | opponentLeaderKilled |
P101086
|
FINISHED |
| Object | Kitbuqa |
—
|
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: Kitbuqa | Statement: [Battle of Ain Jalood, opponentLeaderKilled, Kitbuqa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opponentLeaderKilled Context triple: [Battle of Ain Jalood, opponentLeaderKilled, Kitbuqa]
-
A.
keyFigureKilled
Indicates that a central or important individual was killed, typically as a significant event in the context.
-
B.
combatantLeaderKilledOrMortallyWounded
chosen
Indicates that the leader of a combatant force was killed outright or suffered wounds that were fatal in the context of the conflict or engagement.
-
C.
numberOfConfirmedKills
Indicates the total count of individuals that an entity is reported or confirmed to have killed.
-
D.
killedBy
Indicates that one entity caused the death of another entity.
-
E.
killedOrCaptured
Indicates that one entity has either killed or taken another entity into custody or control.
- 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_69ee5b4a77e08190bfcb5f8ecdc55abd |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60d1ddcc08190a133f90d4e92102f |
completed | May 2, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69f5b007ec1c819092e2c3605933f60b |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:55 p.m.