Triple
T1282368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chertsey |
E27353
|
entity |
| Predicate | abbeyDissolved |
P133
|
FINISHED |
| Object | 16th 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: 16th century | Statement: [Chertsey, abbeyDissolved, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abbeyDissolved Context triple: [Chertsey, abbeyDissolved, 16th century]
-
A.
dateAbolished
Indicates the date on which something (such as an institution, law, practice, or position) was officially ended or abolished.
-
B.
dissolvedOrAbolished
chosen
Indicates that an organization, institution, or formal entity has been officially terminated, disbanded, or ceased to exist.
-
C.
formerCathedral
Indicates that a building once held the status and function of a cathedral but no longer does.
-
D.
disestablishmentEvent
Indicates the event or process by which an organization, institution, or system is formally dissolved, abolished, or stripped of its official status.
-
E.
archdeaconry
Indicates that one entity holds the ecclesiastical office or jurisdiction of an archdeacon over another entity or area.
- 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_69a496d3710c8190955dee8bc0dacb50 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c0b47be08190828a1c0a11d94ce8 |
completed | March 1, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69a4bee276d8819092f71c5a1140bb61 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.