Triple
T6479368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chertsey Abbey |
E146149
|
entity |
| Predicate | wasDissolvedIn |
P62226
|
FINISHED |
| Object | 1537 |
—
|
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: 1537 | Statement: [Chertsey Abbey, wasDissolvedIn, 1537]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasDissolvedIn Context triple: [Chertsey Abbey, wasDissolvedIn, 1537]
-
A.
wasDissolvedAfter
Indicates that one entity ceased to exist or operate at a later point in time than another entity’s dissolution.
-
B.
dissolvedOrAbolished
Indicates that an organization, institution, or formal entity has been officially terminated, disbanded, or ceased to exist.
-
C.
dissolvedByMerger
Indicates that an entity ceased to exist as an independent entity because it was legally combined into another entity through a merger.
-
D.
endedByDissolution
Indicates that a relationship, agreement, or entity was terminated specifically through a formal dissolution process.
-
E.
disbandedAt
chosen
Indicates the time or date at which an organized group, body, or entity formally ceased to exist or operate.
- 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_69c008fec7408190af7b146dc63d9750 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a4e764c819086828bb841f588e0 |
completed | March 22, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69c0673f6d48819080e10c85155c7195 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:51 p.m.