Triple
T28720342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lakhdar Boumediene |
E730075
|
entity |
| Predicate | detentionWithoutCharge |
P165262
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Lakhdar Boumediene, detentionWithoutCharge, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: detentionWithoutCharge Context triple: [Lakhdar Boumediene, detentionWithoutCharge, true]
-
A.
detainsUnder
Indicates that one entity holds another in custody or confinement under a specific legal authority, provision, or condition.
-
B.
detainedFor
Indicates that one entity is being held in custody or confinement because of, or as a consequence of, another entity (such as a reason, charge, or event).
-
C.
coDetainee
Indicates that two or more individuals are detained or imprisoned together in the same facility or under the same custodial authority.
-
D.
detainedAfter
Indicates that one entity is held in custody or confinement following another specified event or action.
-
E.
detentionCondition
Indicates the specific terms, circumstances, or requirements under which a person is held in detention.
- 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_69f043e91fe48190b73bcd8e08d433e0 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f657087c6481908ccf4599778d275d |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 28, 2026, 5:53 a.m.