Triple
T2649231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christ Church Cathedral |
E53856
|
entity |
| Predicate | cryptStatus |
P5511
|
FINISHED |
| Object | one of the largest cathedral crypts in Britain and Ireland |
—
|
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: one of the largest cathedral crypts in Britain and Ireland | Statement: [Christ Church Cathedral, cryptStatus, one of the largest cathedral crypts in Britain and Ireland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cryptStatus Context triple: [Christ Church Cathedral, cryptStatus, one of the largest cathedral crypts in Britain and Ireland]
-
A.
cryptanalysisStatus
Indicates the current state or outcome of efforts to analyze or break a cryptographic system or cipher.
-
B.
hasCrypt
chosen
Indicates that one entity possesses, contains, or is associated with a crypt belonging to or located within it.
-
C.
securityStatus
Indicates the current level or condition of protection, risk, or vulnerability associated with an entity or system.
-
D.
cipherCategory
Indicates that one item is classified as a type or category of cipher to which the other item belongs.
-
E.
usesEncryptionAlgorithm
Indicates that one entity applies or relies on a specific encryption algorithm to protect data or communications.
- 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.