Triple

T26605012
Position Surface form Disambiguated ID Type / Status
Subject Federal Correctional Institution Coleman E667743 entity
Predicate securityLevel_FCI Coleman Low P60827 FINISHED
Object low security 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: low security | Statement: [Federal Correctional Institution Coleman, securityLevel_FCI Coleman Low, low security]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: securityLevel_FCI Coleman Low
Context triple: [Federal Correctional Institution Coleman, securityLevel_FCI Coleman Low, low security]
  • A. securityLevelComponents
    Indicates that a particular security level is composed of, or associated with, a specific set of component elements or factors.
  • B. isSecureFacility
    Indicates that a facility has protections, controls, and safeguards in place to prevent unauthorized access, tampering, or security breaches.
  • C. typicalSecurityLevel chosen
    Indicates the usual or standard security level that is generally applied or expected in a given context or system.
  • D. hasCleanlinessLevel
    Indicates the degree or state of cleanliness associated with an entity.
  • E. amenityLevel
    Indicates the degree or quality of facilities, services, or conveniences provided in relation to something.
  • 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_69ee9cfd20348190bb1255d2603efb7a completed April 26, 2026, 11:17 p.m.
NER Named-entity recognition batch_69f661b58ac48190907b6c6e9ccc2c59 completed May 2, 2026, 8:42 p.m.
PD Predicate disambiguation batch_69f660eea4648190b0d5e24293607813 completed May 2, 2026, 8:39 p.m.
Created at: April 27, 2026, 2:14 a.m.