Triple
T19373649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ripon Cathedral |
E484607
|
entity |
| Predicate | earliestCryptDate |
P69130
|
FINISHED |
| Object | c. 672 |
—
|
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: c. 672 | Statement: [Ripon Cathedral, earliestCryptDate, c. 672]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestCryptDate Context triple: [Ripon Cathedral, earliestCryptDate, c. 672]
-
A.
earliestDate
Indicates the earliest point in time at which an associated event, state, or relationship is considered to begin or be valid.
-
B.
earliestVersionDate
Indicates the date on which the earliest known or first version of an entity was created, released, or became valid.
-
C.
firstBlockMinedDate
Indicates the date on which the first block associated with the entity was mined.
-
D.
firstDeployedAt
Indicates the date and time when an entity was initially put into use or made operational.
-
E.
earliestStrataDate
chosen
Indicates the earliest known or recorded date associated with a particular geological or archaeological stratum.
- 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_69d8e8d305088190ad13571532aa454c |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e61a59f8cc8190b314cba95c25f2a0 |
completed | April 20, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69e4fd54f8e48190956e73dd8969164a |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:35 p.m.