Triple
T24133178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jamal al-Badawi |
E598008
|
entity |
| Predicate | escapeEvent |
P54365
|
FINISHED |
| Object | 2003 prison escape in Yemen |
—
|
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: 2003 prison escape in Yemen | Statement: [Jamal al-Badawi, escapeEvent, 2003 prison escape in Yemen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: escapeEvent Context triple: [Jamal al-Badawi, escapeEvent, 2003 prison escape in Yemen]
-
A.
captureEvent
Indicates an event in which one entity successfully takes control, possession, or custody of another entity.
-
B.
escapeStatus
chosen
Indicates whether an entity has escaped, is in the process of escaping, or has not escaped from a given situation or confinement.
-
C.
escapeBehavior
Indicates a relationship where an entity actively attempts to avoid, flee from, or get away from another entity, situation, or constraint.
-
D.
closureEvent
Indicates an event or action in which something is formally brought to an end, completed, or shut down.
-
E.
escapeMechanism
Indicates a means or method by which an entity avoids, evades, or breaks free from a threat, constraint, or controlling influence.
- 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_69e288c808b881909fed7d18f04bcbbe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1df79bfd08190970ed1b3f14ebc8b |
completed | April 29, 2026, 10:37 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:26 p.m.