Triple
T8654470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander Nevsky Cathedral |
E205379
|
entity |
| Predicate | constructionPaused |
P32859
|
FINISHED |
| Object | 1880s |
—
|
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: 1880s | Statement: [Alexander Nevsky Cathedral, constructionPaused, 1880s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructionPaused Context triple: [Alexander Nevsky Cathedral, constructionPaused, 1880s]
-
A.
constructionHalted
chosen
Indicates that an ongoing construction activity or project has been stopped or suspended before completion.
-
B.
constructionInterruptedBy
Indicates that an ongoing construction process is halted, delayed, or disrupted due to the actions or occurrence of another specified entity or event.
-
C.
constructionResumed
Indicates that previously halted construction activity on an entity or project has started again.
-
D.
constructionCompleted
Indicates that a construction process or project has been fully finished and reached its completed state.
-
E.
constructionPhase
Indicates the specific stage or period an entity is in within an overall construction or building process.
- 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_69ca8350897c819086cde7596fbe5fe7 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc48432568819093b9a867b4f62b78 |
completed | March 31, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69cc45619460819091e83ffdec99c865 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:29 p.m.