Triple
T34852565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corsham Court |
E1004638
|
entity |
| Predicate | hasMajorRemodellingPeriod |
P54016
|
FINISHED |
| Object | 18th 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: 18th century | Statement: [Corsham Court, hasMajorRemodellingPeriod, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorRemodellingPeriod Context triple: [Corsham Court, hasMajorRemodellingPeriod, 18th century]
-
A.
hasMajorReconstruction
Indicates that an entity has undergone a significant or extensive reconstruction or renovation.
-
B.
hasMajorWork
Indicates that an entity (typically a person, creator, or organization) is associated with a significant or principal work they produced or are best known for.
-
C.
majorRedevelopmentPeriod
chosen
Indicates a time span during which a place or structure underwent significant redevelopment or large-scale renovation.
-
D.
rebuiltOrModifiedDuring
Indicates that an existing entity was reconstructed, renovated, or otherwise significantly altered during a specified time period or event.
-
E.
remodellingEndYear
Indicates the calendar year in which a remodelling process or project was completed.
- 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_69f76dba76f0819090643cba102c41ec |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a01ca0db6f08190bed479584114e63d |
completed | May 11, 2026, 12:22 p.m. |
| PD | Predicate disambiguation | batch_6a01c96ff4a08190a4fbf0cebbda95b4 |
completed | May 11, 2026, 12:20 p.m. |
Created at: May 3, 2026, 4 p.m.