Triple
T2649216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christ Church Cathedral |
E53856
|
entity |
| Predicate | elevatedToCathedral |
P27686
|
FINISHED |
| Object | 12th century |
—
|
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: 12th century | Statement: [Christ Church Cathedral, elevatedToCathedral, 12th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevatedToCathedral Context triple: [Christ Church Cathedral, elevatedToCathedral, 12th century]
-
A.
cathedral
Indicates that an entity is a cathedral, i.e., it has the status or function of a principal church, typically one that is the seat of a bishop.
-
B.
elevationToCathedral
chosen
Indicates the formal act or process by which a church is raised in status to become a cathedral.
-
C.
elevatedToBasilica
Indicates that a church has been formally raised in status and designated as a basilica by ecclesiastical authority.
-
D.
coCathedral
Indicates that a church shares the status and functions of a cathedral with another cathedral within the same diocese or ecclesiastical jurisdiction.
-
E.
cathedralFeature
Indicates that one entity is a distinctive architectural or structural feature of a cathedral.
- 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_69ab495e192081909c77b622e8e7e15a |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd91ca1288190ba302b04bac4c153 |
completed | March 7, 2026, 7:51 a.m. |
| PD | Predicate disambiguation | batch_69abd814298c8190952f05aed43f6bb8 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.