Triple
T36781706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Isotope |
E908785
|
entity |
| Predicate | hijackersCaptured |
P12811
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Operation Isotope, hijackersCaptured, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hijackersCaptured Context triple: [Operation Isotope, hijackersCaptured, 2]
-
A.
numberOfHijackers
chosen
Indicates the quantity of individuals who carried out or attempted to carry out a hijacking in the described event or context.
-
B.
casualtiesHijackers
Indicates that the hijackers caused or were responsible for casualties (deaths or injuries) among others.
-
C.
hostages
Indicates that one party is forcibly holding another party captive, typically to compel a third party to meet certain demands or conditions.
-
D.
captivesTaken
Indicates that one entity has taken another entity or group into captivity, holding them against their will.
-
E.
numberOfPakistaniPrisonersTaken
Indicates the quantity of Pakistani prisoners that were captured or taken into custody in a given context.
- 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_69f7c9f71e70819089f722234376df65 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.