Triple
T36781704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Isotope |
E908785
|
entity |
| Predicate | casualtiesHostagesKilled |
P88183
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Operation Isotope, casualtiesHostagesKilled, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: casualtiesHostagesKilled Context triple: [Operation Isotope, casualtiesHostagesKilled, 1]
-
A.
numberOfHostagesKilled
chosen
Indicates the number of hostages who were killed in the context of a specific event or situation.
-
B.
numberOfHostages
Indicates the quantity of hostages involved in a particular situation, event, or context.
-
C.
causeOfHostageDeaths
Indicates that the subject is responsible for bringing about the deaths of the hostages.
-
D.
hostages
Indicates that one party is forcibly holding another party captive, typically to compel a third party to meet certain demands or conditions.
-
E.
casualtiesHijackers
Indicates that the hijackers caused or were responsible for casualties (deaths or injuries) among others.
- 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_69f76e798aa08190ace31098d1b13e9f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:12 p.m.