Triple
T8811960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santa Rosa County Jail |
E209684
|
entity |
| Predicate | detainsFor |
P33388
|
FINISHED |
| Object | misdemeanor offenses |
—
|
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: misdemeanor offenses | Statement: [Santa Rosa County Jail, detainsFor, misdemeanor offenses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: detainsFor Context triple: [Santa Rosa County Jail, detainsFor, misdemeanor offenses]
-
A.
detainedFor
chosen
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).
-
B.
detainedBy
Indicates that an entity is being held in custody or confinement by another entity, typically an authority or controlling party.
-
C.
detainedAfter
Indicates that one entity is held in custody or confinement following another specified event or action.
-
D.
detainedUntil
Indicates that an entity is held in custody or confinement up to a specified time or until a particular condition is met.
-
E.
usedToDetain
Indicates that something serves or functioned as a means, tool, or facility for holding or confining someone against their will.
- 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_69ca8363f3308190a47e3f1ebd51f613 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5feed07881909bbe116ae359346a |
completed | March 31, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1f28ec8190a34311cb412920c2 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:45 p.m.