Triple
T9904135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prune Street Debtors' Prison, Philadelphia |
E182361
|
entity |
| Predicate | notablePrisonerOccupation |
P18550
|
FINISHED |
| Object | financier |
—
|
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: financier | Statement: [Prune Street Debtors' Prison, Philadelphia, notablePrisonerOccupation, financier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePrisonerOccupation Context triple: [Prune Street Debtors' Prison, Philadelphia, notablePrisonerOccupation, financier]
-
A.
notablePrisoner
Indicates that a person is recognized as a significant or noteworthy inmate of a particular prison or detention facility.
-
B.
notablePrison
Indicates that an entity is a prison of particular significance or prominence in relation to another entity.
-
C.
hasNotableCategoryOfPrisoners
chosen
Indicates that a prison is known for housing a specific, notable category or type of prisoners.
-
D.
prisonerOf
Indicates that one entity is held in custody or confinement by another entity, typically under legal or authoritative control.
-
E.
hasPrisoners
Indicates that an entity holds or contains one or more individuals who are imprisoned or detained.
- 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_69ca82876f8081909cf75df0f99bb13f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb4e4f92c81908e38509416f19c78 |
completed | April 2, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69cd1d8c584081908b73de75eb18e438 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:40 p.m.