Triple
T4009473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cathedral of Christ the Saviour |
E90606
|
entity |
| Predicate | reconstructionCompletion |
P15976
|
FINISHED |
| Object | 2000 |
—
|
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: 2000 | Statement: [Cathedral of Christ the Saviour, reconstructionCompletion, 2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reconstructionCompletion Context triple: [Cathedral of Christ the Saviour, reconstructionCompletion, 2000]
-
A.
reconstructionStatus
chosen
Indicates the current state or phase of a reconstruction process that an entity is undergoing or has undergone.
-
B.
reconstructionBuilt
Indicates that one entity carried out or was responsible for constructing a rebuilt or restored version of another entity.
-
C.
reconstructedAfter
Indicates that one entity has been rebuilt, restored, or reassembled following the occurrence or existence of another entity or event.
-
D.
reconstructionStart
Indicates the point in time or event at which a reconstruction process or activity begins.
-
E.
reconstructedDuring
Indicates that an entity was rebuilt, restored, or significantly repaired within a specified time period or event.
- 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_69aed95e44088190aff7d90a151b1b20 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaec08dc8190a341809059554f84 |
completed | March 9, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69aef8fa6fec81909b1190ecbba61410 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:34 p.m.