Triple
T26605023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Correctional Institution Coleman |
E667743
|
entity |
| Predicate | isPrisonComplex |
P173687
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Federal Correctional Institution Coleman, isPrisonComplex, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrisonComplex Context triple: [Federal Correctional Institution Coleman, isPrisonComplex, true]
-
A.
hasNearbyPrisonComplex
Indicates that one location is situated close to a prison complex.
-
B.
majorPenitentiary
Indicates that an entity serves as a primary or principal penitentiary (major prison) within a given system or jurisdiction.
-
C.
isPenalInstitution
Indicates that an entity functions as a facility where individuals are legally confined as punishment or while awaiting legal proceedings.
-
D.
prisonLocatedIn
Indicates that a prison is situated within or at a specific geographic or administrative location.
-
E.
isFederalPrison
Indicates that the entity functions as a prison operated or administered by a federal government authority.
- F. None of above. chosen
Provenance (4 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_69ee9cfd20348190bb1255d2603efb7a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6b9a84ff88190ab5a71f7ef1e0dac |
completed | May 3, 2026, 2:57 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b8fe147881908ba17483c7b13f05 |
completed | May 3, 2026, 2:54 a.m. |
Created at: April 27, 2026, 2:14 a.m.