Triple
T30146382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canon Steward |
E766264
|
entity |
| Predicate | isClericalOfficeFor |
P133190
|
FINISHED |
| Object | Canon of Windsor |
—
|
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: Canon of Windsor | Statement: [Canon Steward, isClericalOfficeFor, Canon of Windsor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isClericalOfficeFor Context triple: [Canon Steward, isClericalOfficeFor, Canon of Windsor]
-
A.
isClericalOfficeIn
chosen
Indicates that a clerical or administrative office is located within or belongs to a specified place or organization.
-
B.
isClericalBodyFor
Indicates that one entity functions as the official clerical or administrative body responsible for serving, supporting, or governing another entity.
-
C.
hasClericalFunction
Indicates that an entity performs, is responsible for, or is associated with a clerical or administrative function.
-
D.
hasReligiousOffice
Indicates that an entity holds or occupies a specific religious role, position, or office within a religious organization or tradition.
-
E.
isClericIn
Indicates that an entity serves or functions as a cleric within a specified organization, location, or group.
- 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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67e8c266081909c00fbe8a1791436 |
completed | May 2, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:19 p.m.