Triple
T3969322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Penitentiary, Leavenworth |
E92289
|
entity |
| Predicate | hasSecurityMeasures |
P32681
|
FINISHED |
| Object | perimeter fencing |
—
|
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: perimeter fencing | Statement: [United States Penitentiary, Leavenworth, hasSecurityMeasures, perimeter fencing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecurityMeasures Context triple: [United States Penitentiary, Leavenworth, hasSecurityMeasures, perimeter fencing]
-
A.
safeguardingMeasuresInclude
chosen
Indicates that certain specific protective or security measures are contained within, or form part of, a broader set of safeguarding measures.
-
B.
protectionMeasures
Indicates actions or safeguards implemented to prevent harm, damage, or risk to someone or something.
-
C.
hasSecurityNotion
Indicates that one entity possesses, defines, or is associated with a particular concept or notion of security in relation to another entity or context.
-
D.
hasSecurityPresence
Indicates that some form of security personnel, system, or measures are present at or associated with an entity or location.
-
E.
hasSecurityStandard
Indicates that an entity complies with, follows, or is governed by a specified security standard or framework.
- 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_69aed96624188190ac8c45bb57ab72b5 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaca33e4819091957c7915857a42 |
completed | March 9, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69aef8f252b081909749d40440d372b2 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:32 p.m.