Triple
T6699884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archdeacon of Leicester |
E152850
|
entity |
| Predicate | officeIn |
P72510
|
FINISHED |
| Object | Church of England hierarchy |
—
|
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: Church of England hierarchy | Statement: [Archdeacon of Leicester, officeIn, Church of England hierarchy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeIn Context triple: [Archdeacon of Leicester, officeIn, Church of England hierarchy]
-
A.
office
Indicates that an entity holds or occupies an official position, role, or post within an organization or institution.
-
B.
officeUnder
Indicates that one office is subordinate to, managed by, or organizationally within the authority of another office.
-
C.
officeIsIn
Indicates that one office is located within or inside another specified place or building.
-
D.
worksWithOffice
Indicates that an entity collaborates or is professionally associated with a particular office or office-based organization.
-
E.
inOfficeFrom
Indicates that an entity holds a particular office or position starting from a specified date or time.
- 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_69c68807adbc8190b8632df42b39eda0 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d16897e48190b43eda2206b14d6a |
completed | March 27, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69c6d089c7488190a00853fb12f53b2a |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d1668a7c8190ae93951f9ba2df10 |
completed | March 27, 2026, 6:50 p.m. |
Created at: March 27, 2026, 2:05 p.m.