Triple
T9653998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Escambia County Sheriff’s Office |
E233403
|
entity |
| Predicate | typeOfDetentionFacilityOperated |
P50528
|
FINISHED |
| Object | county jail |
—
|
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: county jail | Statement: [Escambia County Sheriff’s Office, typeOfDetentionFacilityOperated, county jail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfDetentionFacilityOperated Context triple: [Escambia County Sheriff’s Office, typeOfDetentionFacilityOperated, county jail]
-
A.
placeOfDetention
Indicates the location or facility where an entity is or was held in detention.
-
B.
detentionType
chosen
Indicates the specific category or form of detention applied to an entity within a custodial or restrictive context.
-
C.
prisonType
Indicates the specific category or classification of a prison associated with an entity.
-
D.
operatedPrison
Indicates that an entity managed, ran, or was responsible for the day-to-day operation of a particular prison.
-
E.
detaineeStatus
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.
- 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_69ca848c1ba88190b84b410cd14627fc |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9bda8e7881908b0e36b91a8d3891 |
completed | April 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b0263081908cf6df3eb07d71b0 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:13 p.m.