Triple
T21407535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ragley Hall |
E528077
|
entity |
| Predicate | significantRebuildingDate |
P8589
|
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: [Ragley Hall, significantRebuildingDate, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantRebuildingDate Context triple: [Ragley Hall, significantRebuildingDate, 18th century]
-
A.
rebuiltOn
Indicates that one entity has been reconstructed, restored, or built again on, over, or using the foundation, structure, or basis of another entity.
-
B.
reconstructionOrRestorationDate
chosen
Indicates the date on which an entity was reconstructed or restored after damage, alteration, or deterioration.
-
C.
reconstructionBuiltAt
Indicates that a reconstruction of something was built or carried out at a specific location or site.
-
D.
redevelopmentDate
Indicates the date on which an existing structure, area, or asset is scheduled for or has undergone redevelopment.
-
E.
hasRebuiltDate
Indicates the date on which something was rebuilt or reconstructed.
- 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_69e0b520ee3c8190abddbee7e37e834c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b1b1acd881908556981ed788340c |
completed | April 22, 2026, 11:32 a.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:32 p.m.