Triple
T13381460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delapré Abbey |
E319326
|
entity |
| Predicate | majorRestorationCompletedInYear |
P8589
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [Delapré Abbey, majorRestorationCompletedInYear, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorRestorationCompletedInYear Context triple: [Delapré Abbey, majorRestorationCompletedInYear, 2017]
-
A.
majorRestorationLocation
Indicates the primary place where a significant restoration or refurbishment of an object, structure, or work was carried out.
-
B.
reconstructionOrRestorationDate
chosen
Indicates the date on which an entity was reconstructed or restored after damage, alteration, or deterioration.
-
C.
significantRestoration
Indicates that an entity has undergone a major or substantial restoration effort that notably improves or returns it to a previous condition.
-
D.
majorRevisionYear
Indicates the year in which a significant or primary revision of something (such as a work, document, or standard) was made.
-
E.
reconstructionYear
Indicates the year in which something was rebuilt, restored, or reconstructed after damage, alteration, or destruction.
- 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_69d806b886bc8190b676e7768b8e01c5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dadce694788190881d1feac5b75720 |
completed | April 11, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69d9a03189908190a784a2755f8d81e1 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:33 p.m.