Triple
T31952848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Detention Site Cobalt |
E815827
|
entity |
| Predicate | detaineesHeldWithout |
P165262
|
FINISHED |
| Object | formal charges |
—
|
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: formal charges | Statement: [Detention Site Cobalt, detaineesHeldWithout, formal charges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: detaineesHeldWithout Context triple: [Detention Site Cobalt, detaineesHeldWithout, formal charges]
-
A.
detainedPopulation
Indicates that a population of individuals is being held in custody or confinement, typically by legal or governmental authority.
-
B.
detentionWithoutCharge
chosen
Indicates that an entity is being held in custody by authorities without having formal charges filed against them.
-
C.
coDetainee
Indicates that two or more individuals are detained or imprisoned together in the same facility or under the same custodial authority.
-
D.
detainsUnder
Indicates that one entity holds another in custody or confinement under a specific legal authority, provision, or condition.
-
E.
detainedPrisonersFrom
Indicates that an authority is holding prisoners who originate from or are associated with a specified place or source.
- 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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b2ac9bd481909a1e8adb4e294262 |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:08 a.m.