Triple
T16963230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indiana state prisons |
E411479
|
entity |
| Predicate | exclude |
P3119
|
FINISHED |
| Object | most federal prisoners |
—
|
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: most federal prisoners | Statement: [Indiana state prisons, exclude, most federal prisoners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exclude Context triple: [Indiana state prisons, exclude, most federal prisoners]
-
A.
excludes
chosen
Indicates that one entity deliberately omits, leaves out, or does not allow the inclusion of another entity within a set, group, or context.
-
B.
excludedFrom
Indicates that one entity is deliberately not included within the scope, membership, or applicability of another entity or set.
-
C.
excludesSense
Indicates that one sense or interpretation explicitly rules out or is incompatible with another sense.
-
D.
entailExcludes
Indicates that the truth or occurrence of one statement or condition entails that another statement or condition cannot be true or occur simultaneously.
-
E.
exclusiveTo
Indicates that something is restricted or limited to a specific entity, group, or context and not shared with others.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d0a1f6308190af5ad171630dacbf |
completed | April 18, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69e32b9cddf88190bc42709604047353 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.