Triple
T6763205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chelmsford Cathedral |
E154646
|
entity |
| Predicate | cathedralStatusGranted |
P21120
|
FINISHED |
| Object | 1914 |
—
|
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: 1914 | Statement: [Chelmsford Cathedral, cathedralStatusGranted, 1914]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cathedralStatusGranted Context triple: [Chelmsford Cathedral, cathedralStatusGranted, 1914]
-
A.
hasCathedralStatusGrantedBy
Indicates that cathedral status has been formally conferred on something (typically a church or building) by a specified granting authority.
-
B.
cathedralStatus
Indicates that an entity holds the official status or designation of a cathedral within a religious or ecclesiastical context.
-
C.
hasCathedralStatusSince
chosen
Indicates the point in time from which something has held the official status of a cathedral.
-
D.
hasCathedralBasilicaStatus
Indicates that an entity (typically a church) holds the official ecclesiastical designation of a cathedral basilica.
-
E.
cathedralRank
Indicates that an entity holds the status or rank of a cathedral within an ecclesiastical or organizational hierarchy.
- 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_69c688109c1c8190added9a221292af0 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d327e37081909d576e6eff9eec97 |
completed | March 27, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69c6d09227108190b253b91967831a85 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:12 p.m.