Triple
T30742798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sumela Monastery |
E782735
|
entity |
| Predicate | closedForRestorationFrom |
P56011
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [Sumela Monastery, closedForRestorationFrom, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closedForRestorationFrom Context triple: [Sumela Monastery, closedForRestorationFrom, 2015]
-
A.
closedForReconstructionTo
Indicates that access or use of something is prohibited for a party because it is undergoing reconstruction.
-
B.
hasRestoration
Indicates that an entity has undergone, is undergoing, or is associated with a process of repair, renewal, or restoration.
-
C.
closedFor
chosen
Indicates that an entity is not available or accessible for use, entry, or operation during a specified time, condition, or reason.
-
D.
laterRestored
Indicates that something previously altered, damaged, or removed was subsequently brought back to its earlier state or condition.
-
E.
closedForProduction
Indicates that an entity (such as a facility, system, or resource) is temporarily unavailable or shut down due to ongoing production activities or processes.
- 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: April 29, 2026, 8:38 p.m.