Triple
T16963207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indiana state prisons |
E411479
|
entity |
| Predicate | includeFacilityType |
P2836
|
FINISHED |
| Object | adult male prison |
—
|
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: adult male prison | Statement: [Indiana state prisons, includeFacilityType, adult male prison]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includeFacilityType Context triple: [Indiana state prisons, includeFacilityType, adult male prison]
-
A.
hasFacilityType
chosen
Indicates that an entity possesses or is associated with a specific type or category of facility.
-
B.
fccFacilityType
Indicates the specific type or classification of a facility as defined by the FCC (Federal Communications Commission).
-
C.
designedFacilityType
Indicates the type or category of facility that something (such as a plan, system, or component) is specifically designed for.
-
D.
appliesToFacility
Indicates that something (such as a rule, policy, condition, or attribute) is relevant to, valid for, or in effect at a particular facility.
-
E.
usedAtFacilityType
Indicates that something is utilized or applied within a facility of a specified type.
- 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.