Triple
T32716974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kenwood House, London |
E836545
|
entity |
| Predicate | remodellingEndYear |
P175037
|
FINISHED |
| Object | 1779 |
—
|
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: 1779 | Statement: [Kenwood House, London, remodellingEndYear, 1779]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: remodellingEndYear Context triple: [Kenwood House, London, remodellingEndYear, 1779]
-
A.
remodellingStartYear
Indicates the year in which a remodelling process or renovation of the subject entity began.
-
B.
reconstructionYear
Indicates the year in which something was rebuilt, restored, or reconstructed after damage, alteration, or destruction.
-
C.
rebuiltApproximateEndYear
Indicates that an entity was rebuilt, with the specified year representing an approximate (not exact) end date of the rebuilding process.
-
D.
renovatedAfter
Indicates that one entity was renovated at a later time than another entity.
-
E.
renovationYear
Indicates the year in which an entity underwent renovation or significant refurbishment.
- F. None of above. chosen
Provenance (4 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_69f34935455881909088975d79460418 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6cd9bae8c8190b528641499162a75 |
completed | May 3, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6cd119cac8190a0b3ebe8b9c742c2 |
completed | May 3, 2026, 4:20 a.m. |
Created at: May 1, 2026, 1:11 a.m.