Triple
T27535377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Truro |
E695080
|
entity |
| Predicate | cathedralProvince |
P162484
|
FINISHED |
| Object | Province of Canterbury |
—
|
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: Province of Canterbury | Statement: [Truro, cathedralProvince, Province of Canterbury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cathedralProvince Context triple: [Truro, cathedralProvince, Province of Canterbury]
-
A.
cathedralChurch
Indicates that one church serves as the cathedral (principal church and episcopal seat) of another ecclesiastical jurisdiction or entity.
-
B.
hasProCathedral
Indicates that one entity serves as or possesses a pro-cathedral (a church temporarily acting as a cathedral) in relation to another entity.
-
C.
cathedralServed
Indicates that one entity functioned in an official or service role for, or on behalf of, a cathedral.
-
D.
cathedralRank
Indicates that an entity holds the status or rank of a cathedral within an ecclesiastical or organizational hierarchy.
-
E.
coCathedral
Indicates that a church shares the status and functions of a cathedral with another cathedral within the same diocese or ecclesiastical jurisdiction.
- 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_69ef538608b081908b9f659bb09d5e0f |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62f5996508190894a769a5199945d |
completed | May 2, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69f623ac3a9c8190a6ee0c137b09e4b0 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f624c006788190a2f4d5015c96463f |
completed | May 2, 2026, 4:22 p.m. |
Created at: April 27, 2026, 1:28 p.m.