Triple
T30510389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Correctional Institution, Sheridan |
E776400
|
entity |
| Predicate | adjacentFacilitySecurityLevel |
P43566
|
FINISHED |
| Object | minimum |
—
|
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: minimum | Statement: [Federal Correctional Institution, Sheridan, adjacentFacilitySecurityLevel, minimum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adjacentFacilitySecurityLevel Context triple: [Federal Correctional Institution, Sheridan, adjacentFacilitySecurityLevel, minimum]
-
A.
adjacentFacilitySecurityClass
chosen
Indicates that two facilities located next to each other share a specified level or classification of security.
-
B.
adjacentBuildingFunction
Indicates that two buildings located next to each other have a specified functional relationship or usage connection.
-
C.
isSecureFacility
Indicates that a facility has protections, controls, and safeguards in place to prevent unauthorized access, tampering, or security breaches.
-
D.
adjacentToInfrastructure
Indicates that one entity is located directly next to or in immediate proximity to a piece of infrastructure.
-
E.
isAdjacentTo
Indicates that one entity is directly next to or bordering another without anything of the same type in between.
- 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_69f2249a155c8190b1d512106007e9bb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 29, 2026, 8:16 p.m.