Triple
T17640555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union County jail |
E429211
|
entity |
| Predicate | intakeType |
P42668
|
FINISHED |
| Object | individuals arrested within Union County |
—
|
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: individuals arrested within Union County | Statement: [Union County jail, intakeType, individuals arrested within Union County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intakeType Context triple: [Union County jail, intakeType, individuals arrested within Union County]
-
A.
intake
Indicates the act of taking something in or consuming it, such as food, drink, or other substances, into a system or organism.
-
B.
intakeLocation
chosen
Indicates the place or facility where an entity is initially received, admitted, or taken in.
-
C.
airIntakeType
Indicates the type or configuration of the system or mechanism used to draw air into an engine or device.
-
D.
isTypicallyConsumedFrom
Indicates that one entity is most commonly eaten or drunk using, contained in, or taken from the other entity.
-
E.
gutType
Indicates the type or classification of a digestive tract or gut associated with an entity.
- 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.