Triple
T2649232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christ Church Cathedral |
E53856
|
entity |
| Predicate | cryptDate |
P5511
|
FINISHED |
| Object | 12th–13th 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–13th century | Statement: [Christ Church Cathedral, cryptDate, 12th–13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cryptDate Context triple: [Christ Church Cathedral, cryptDate, 12th–13th century]
-
A.
hasCrypt
chosen
Indicates that one entity possesses, contains, or is associated with a crypt belonging to or located within it.
-
B.
cipherCategory
Indicates that one item is classified as a type or category of cipher to which the other item belongs.
-
C.
encryptionDirection
Indicates the direction in which data is being encrypted, specifying whether it is going from source to destination or vice versa.
-
D.
ciphertextExpansion
Indicates that applying the encryption process to the input increases its length, specifying how much the ciphertext expands relative to the original data.
-
E.
coDecipherer
Indicates that two or more entities jointly participated in deciphering or decoding something together.
- 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.