Triple
T17640557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union County jail |
E429211
|
entity |
| Predicate | mayHoldFor |
P9417
|
FINISHED |
| Object | state authorities |
—
|
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: state authorities | Statement: [Union County jail, mayHoldFor, state authorities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayHoldFor Context triple: [Union County jail, mayHoldFor, state authorities]
-
A.
mayHold
chosen
Indicates that one entity is permitted or allowed to possess, contain, or maintain another entity.
-
B.
heldUntil
Indicates that a state, condition, or action continues to hold true up to a specified time or event, and may cease to hold immediately after that point.
-
C.
mayHoldStyle
Indicates that an entity is permitted or able to possess or be associated with a particular style or stylistic attribute.
-
D.
maySuspend
Indicates that one entity has the authority or permission to temporarily suspend another entity or its associated activity, status, or operation.
-
E.
mayDelay
Indicates that one entity has the potential or permission to cause a postponement or slowing of another entity, event, or process.
- 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_69d889e2c2608190b762e76d9b2262f1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46de50bf481909e938613b38f0202 |
completed | April 19, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69e3cddc87188190ac2f049b86038676 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 6:02 a.m.