Triple
T993271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yemeni Revolution of 2011 |
E21437
|
entity |
| Predicate | arrests |
P22280
|
FINISHED |
| Object | thousands of protesters detained |
—
|
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: thousands of protesters detained | Statement: [Yemeni Revolution of 2011, arrests, thousands of protesters detained]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arrests Context triple: [Yemeni Revolution of 2011, arrests, thousands of protesters detained]
-
A.
arrestedFor
Indicates that an authority has taken someone into custody because they are suspected or accused of committing a specified offense or wrongdoing.
-
B.
attemptedArrestBy
Indicates that one entity tried, but may not have succeeded, to place another entity under arrest.
-
C.
reArrested
Indicates that an entity is arrested again after having been previously released or arrested before.
-
D.
dateOfArrest
Indicates the specific date on which an entity was formally arrested by an authority.
-
E.
criminalStatus
Indicates the legal condition of an entity with respect to criminal law, such as whether they are accused, convicted, or cleared of a crime.
- F. None of above. chosen
Provenance (4 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_69a493c476b48190b41fc5e793171cc6 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4c3f7b48190a31308bdc09817c6 |
completed | March 1, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69a4b2adbde48190b07966d0c3179516 |
completed | March 1, 2026, 9:42 p.m. |
| PDg | Predicate description generation | batch_69a4b38723d8819098b861cba5cad4ee |
completed | March 1, 2026, 9:45 p.m. |
Created at: March 1, 2026, 7:41 p.m.