Triple
T7555018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benton County Jail |
E178639
|
entity |
| Predicate | legalStatusOfInmates |
P13715
|
FINISHED |
| Object | in custody |
—
|
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: in custody | Statement: [Benton County Jail, legalStatusOfInmates, in custody]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusOfInmates Context triple: [Benton County Jail, legalStatusOfInmates, in custody]
-
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.
inmates
Indicates that one entity is confined or held as a prisoner within an institution or facility associated with another entity.
-
C.
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.
-
D.
prisonType
Indicates the specific category or classification of a prison associated with an entity.
-
E.
isPenalInstitution
Indicates that an entity functions as a facility where individuals are legally confined as punishment or while awaiting legal proceedings.
- 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_69c69f2da22c8190a50942ac20af70e8 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8d82dd481908351876edc70c4ec |
completed | March 27, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69c6f4daad6c8190af2b8ae88d2c8cb7 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:49 p.m.