Triple
T14707427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fox River State Penitentiary |
E345461
|
entity |
| Predicate | notableFeatureInPlot |
P112925
|
FINISHED |
| Object | infirmary |
—
|
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: infirmary | Statement: [Fox River State Penitentiary, notableFeatureInPlot, infirmary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFeatureInPlot Context triple: [Fox River State Penitentiary, notableFeatureInPlot, infirmary]
-
A.
notableFeatureInStory
chosen
Indicates that a particular feature, element, or characteristic plays a significant or prominent role within a story.
-
B.
notableWorkInPlot
Indicates that a work is prominently featured or plays a significant role within the plot of another work.
-
C.
notableFeatureOn
Indicates that one entity is a prominent or distinguishing feature located on or part of another entity.
-
D.
notableFeat
Indicates that an entity is recognized for having achieved or performed a particularly significant or distinguished feat.
-
E.
notableScene
Indicates that a particular scene is especially significant, memorable, or noteworthy within a work or context.
- 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_69d822e4a8c08190a155df736bb7bc13 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb609965081908f654bcb9eaaa145 |
completed | April 14, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69de657c57ec8190ae0b9bb79a514566 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.