Triple
T1149436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oscarshall |
E23640
|
entity |
| Predicate | reopenedAfterRestoration |
P13045
|
FINISHED |
| Object | 2009 |
—
|
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: 2009 | Statement: [Oscarshall, reopenedAfterRestoration, 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reopenedAfterRestoration Context triple: [Oscarshall, reopenedAfterRestoration, 2009]
-
A.
reopenedAfterReconstruction
Indicates that a place or facility resumed operations after undergoing reconstruction or major rebuilding work.
-
B.
hasRestoration
chosen
Indicates that an entity has undergone, is undergoing, or is associated with a process of repair, renewal, or restoration.
-
C.
restored
Indicates that an entity has returned another entity to a previous or improved state, condition, or position after damage, loss, or alteration.
-
D.
reconstructedAfter
Indicates that one entity has been rebuilt, restored, or reassembled following the occurrence or existence of another entity or event.
-
E.
restoredBy
Indicates that an entity has been returned to a previous or improved state through the actions or intervention 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_69a493f0d32c8190ac74bad3c87f2641 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bd0bed00819091d71983d787a030 |
completed | March 1, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4ee3988190ac89c5ae5b10e316 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.