Triple
T19581253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Trinity Church, Headington Quarry, Oxford |
E489989
|
entity |
| Predicate | hasClergyHouse |
P44856
|
FINISHED |
| Object | parsonage |
—
|
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: parsonage | Statement: [Holy Trinity Church, Headington Quarry, Oxford, hasClergyHouse, parsonage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClergyHouse Context triple: [Holy Trinity Church, Headington Quarry, Oxford, hasClergyHouse, parsonage]
-
A.
hasClergy
Indicates that an organization or institution possesses or is served by members of the clergy.
-
B.
hasClericalStructure
Indicates that an entity possesses an organized clerical or administrative hierarchy or framework.
-
C.
hasParishHouse
chosen
Indicates that a church or parish entity possesses or is associated with a specific parish house building.
-
D.
hasClergyType
Indicates the specific category or role of clergy associated with an entity.
-
E.
hasClergyLikeGroup
Indicates that an entity possesses or is associated with a group functioning in a clergy-like or religious-leadership role.
- 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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e640281b7c8190be44268a58df058f |
completed | April 20, 2026, 3:03 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:42 p.m.