Triple
T15459796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Mary Magdalene, Richmond |
E371865
|
entity |
| Predicate | underwentMajorRebuilding |
P72514
|
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: [St Mary Magdalene, Richmond, underwentMajorRebuilding, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underwentMajorRebuilding Context triple: [St Mary Magdalene, Richmond, underwentMajorRebuilding, 18th century]
-
A.
largelyRebuilt
Indicates that an entity has been substantially reconstructed or renovated, with most of its original structure replaced or significantly altered.
-
B.
hasMajorReconstruction
chosen
Indicates that an entity has undergone a significant or extensive reconstruction or renovation.
-
C.
rebuiltOrExpanded
Indicates that one entity has been reconstructed, enlarged, or otherwise significantly developed from its previous form or state.
-
D.
majorRebuilder
Indicates that an entity plays a primary or leading role in reconstructing, restoring, or significantly rebuilding another entity.
-
E.
rebuiltAsPalace
Indicates that a structure or building was reconstructed or transformed into a palace.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f17663c8190b995c7c3129c90d6 |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded284bd008190b31c53b4f1cebadd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:32 a.m.