Triple
T20310268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosies |
E510218
|
entity |
| Predicate | detainsStatus |
P13715
|
FINISHED |
| Object | pretrial detainees |
—
|
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: pretrial detainees | Statement: [Rosies, detainsStatus, pretrial detainees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: detainsStatus Context triple: [Rosies, detainsStatus, pretrial detainees]
-
A.
detaineeStatus
chosen
Indicates the current legal or custodial condition of a person being detained, such as whether they are in custody, released, or under a specific detention regime.
-
B.
detainedBy
Indicates that an entity is being held in custody or confinement by another entity, typically an authority or controlling party.
-
C.
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).
-
D.
detentionOutcome
Indicates the result or consequence of a detention, such as whether it was continued, ended, or changed in status.
-
E.
detainsUnder
Indicates that one entity holds another in custody or confinement under a specific legal authority, provision, or condition.
- 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_69e0b4c7491c8190961113c4283b10b0 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e677436af88190a046c44fa45b68b4 |
completed | April 20, 2026, 6:58 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:19 a.m.