Triple
T26209305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allington Castle, Kent |
E655439
|
entity |
| Predicate | underwentExtensiveRestoration |
P59927
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Allington Castle, Kent, underwentExtensiveRestoration, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underwentExtensiveRestoration Context triple: [Allington Castle, Kent, underwentExtensiveRestoration, true]
-
A.
significantRestoration
chosen
Indicates that an entity has undergone a major or substantial restoration effort that notably improves or returns it to a previous condition.
-
B.
majorRestorationLocation
Indicates the primary place where a significant restoration or refurbishment of an object, structure, or work was carried out.
-
C.
restorationProject
Indicates a project whose purpose is to repair, renew, or return something to a previous or improved condition.
-
D.
reconstructionOrRestorationDate
Indicates the date on which an entity was reconstructed or restored after damage, alteration, or deterioration.
-
E.
hasRestoration
Indicates that an entity has undergone, is undergoing, or is associated with a process of repair, renewal, or restoration.
- 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_69ee5b49adb4819086545280d4ef6337 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 26, 2026, 8:51 p.m.