Triple
T7242581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Eagle Claw |
E156390
|
entity |
| Predicate | numberOfHostagesTargeted |
P36180
|
FINISHED |
| Object | 52 |
—
|
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: 52 | Statement: [Operation Eagle Claw, numberOfHostagesTargeted, 52]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfHostagesTargeted Context triple: [Operation Eagle Claw, numberOfHostagesTargeted, 52]
-
A.
numberOfHostages
chosen
Indicates the quantity of hostages involved in a particular situation, event, or context.
-
B.
hostages
Indicates that one party is forcibly holding another party captive, typically to compel a third party to meet certain demands or conditions.
-
C.
numberOfHijackers
Indicates the quantity of individuals who carried out or attempted to carry out a hijacking in the described event or context.
-
D.
takesHostageDuring
Indicates that one entity seizes and holds another entity as a hostage in the course of a particular event or action.
-
E.
numberOfVictimsClaimed
Indicates the reported count of victims associated with a particular event, incident, or action.
- 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_69c68827b5e481908dc05e145b2c92d4 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea56756c8190996c2390902f166a |
completed | March 27, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69c6e7644648819096a5e2de5d0dbe97 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:55 p.m.