Triple
T25424414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Correctional Institution, Ray Brook |
E637079
|
entity |
| Predicate | securityClassificationOfPrisonCamp |
P406
|
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, Ray Brook, securityClassificationOfPrisonCamp, minimum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityClassificationOfPrisonCamp Context triple: [Federal Correctional Institution, Ray Brook, securityClassificationOfPrisonCamp, minimum]
-
A.
prisonType
Indicates the specific category or classification of a prison associated with an entity.
-
B.
securityForInmates
Indicates the provision or management of protective measures and safeguards specifically intended for inmates.
-
C.
hasNotableCategoryOfPrisoners
Indicates that a prison is known for housing a specific, notable category or type of prisoners.
-
D.
securityClassification
chosen
Indicates the level or category of security sensitivity or access restriction assigned to an entity.
-
E.
prisonerType
Indicates the classification or category assigned to a prisoner within a correctional or detention system.
- 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f6bf25c881909f049d5393927bfb |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 1:57 p.m.