Triple
T17272057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Florida State Prison |
E419283
|
entity |
| Predicate | hasNotableInmateType |
P18550
|
FINISHED |
| Object | serial killers |
—
|
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: serial killers | Statement: [Florida State Prison, hasNotableInmateType, serial killers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableInmateType Context triple: [Florida State Prison, hasNotableInmateType, serial killers]
-
A.
hasNotableCategoryOfPrisoners
chosen
Indicates that a prison is known for housing a specific, notable category or type of prisoners.
-
B.
notablePrisoner
Indicates that a person is recognized as a significant or noteworthy inmate of a particular prison or detention facility.
-
C.
hasPrisoners
Indicates that an entity holds or contains one or more individuals who are imprisoned or detained.
-
D.
notablePrisonerGuarded
Indicates that a guard was responsible for overseeing or guarding a prisoner who is considered notable or significant.
-
E.
notablePrison
Indicates that an entity is a prison of particular significance or prominence in relation to another entity.
- 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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42f4a3c4c81908a28c9f8bdf648ca |
completed | April 19, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69e3832c3b98819091967ac7e91ba316 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:40 a.m.