Triple
T4157383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panopticon; or, The Inspection-House |
E91448
|
entity |
| Predicate | proposesUseIn |
P34894
|
FINISHED |
| Object | prisons |
—
|
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: prisons | Statement: [Panopticon; or, The Inspection-House, proposesUseIn, prisons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposesUseIn Context triple: [Panopticon; or, The Inspection-House, proposesUseIn, prisons]
-
A.
recommendsUseOf
chosen
Indicates that one entity advises, endorses, or suggests the use of another entity as appropriate or beneficial in a given context.
-
B.
proposes
Indicates that one entity formally suggests or puts forward an idea, plan, or course of action to another entity for consideration or approval.
-
C.
plannedUseOf
Indicates that one entity is intended or designated to be used for a specific purpose, function, or activity involving another entity.
-
D.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
E.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
- 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_69aed9626ebc8190a39de631788bea3e |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0321eee88190871c1d4bf44a5007 |
completed | March 9, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69af018dc90c8190a754b1bfbc802e80 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:44 p.m.