Triple
T1099560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dormition Cathedral |
E24346
|
entity |
| Predicate | reopenedForServicesIn |
P13537
|
FINISHED |
| Object | late 20th 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: late 20th century | Statement: [Dormition Cathedral, reopenedForServicesIn, late 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reopenedForServicesIn Context triple: [Dormition Cathedral, reopenedForServicesIn, late 20th century]
-
A.
openedForThroughService
Indicates that an entity has been made accessible or available specifically for use via a through-service connection or route, rather than as a standalone endpoint.
-
B.
reopeningDate
Indicates the date on which something that was previously closed is opened again for use or access.
-
C.
reopenedForWorship
chosen
Indicates that a previously closed or inactive place of worship has been opened again for religious services or rituals.
-
D.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
-
E.
serviceIn
Indicates that one entity serves, operates, or performs its function within the context, scope, or domain of another entity.
- 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_69a4940542308190ac2a0b1f730b7cfc |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b9be92688190838ce35cd67e01f3 |
completed | March 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69a4b745ef3481909a7ce4647c8567b3 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:43 p.m.