Triple
T26675748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | parish of St Olave, Southwark |
E672449
|
entity |
| Predicate | hadWorkhouse |
P161109
|
FINISHED |
| Object | St Olave’s workhouse |
—
|
NE NERFINISHED |
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: St Olave’s workhouse | Statement: [parish of St Olave, Southwark, hadWorkhouse, St Olave’s workhouse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadWorkhouse Context triple: [parish of St Olave, Southwark, hadWorkhouse, St Olave’s workhouse]
-
A.
housedWorkBy
Indicates that one entity serves as the location or repository where a work created by another entity is kept or displayed.
-
B.
hadMeetingHouse
Indicates that an entity possessed or was associated with a specific meeting house as a place for gatherings or assemblies.
-
C.
wonWork
Indicates that one party has successfully secured or been awarded a particular job, contract, or work opportunity over others.
-
D.
performedLabourAt
Indicates that an entity carried out work or labor activities at a specific place or organization.
-
E.
hadKontorIn
Indicates that an entity maintained or operated a commercial office or trading post in a specified location.
- F. None of above. chosen
Provenance (4 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_69eecda13424819092b17942c4edf722 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f61702ad548190bbc5995748b3ffd2 |
completed | May 2, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f60f24ed608190bffe6c6084fc2f7a |
completed | May 2, 2026, 2:50 p.m. |
Created at: April 27, 2026, 3:16 a.m.