Triple
T27969031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phantom Manor |
E704803
|
entity |
| Predicate | reopenedAfterRefurbishmentOn |
P5418
|
FINISHED |
| Object | 2019-05-03 |
—
|
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: 2019-05-03 | Statement: [Phantom Manor, reopenedAfterRefurbishmentOn, 2019-05-03]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reopenedAfterRefurbishmentOn Context triple: [Phantom Manor, reopenedAfterRefurbishmentOn, 2019-05-03]
-
A.
renovatedAfter
Indicates that one entity was renovated at a later time than another entity.
-
B.
wasRenovatedFor
Indicates that an existing entity underwent renovation specifically to serve the needs, purposes, or use of another entity.
-
C.
reopenedAfterRedevelopment
chosen
Indicates that a place or facility was closed for redevelopment and subsequently opened again once the redevelopment was completed.
-
D.
renovatedBy
Indicates that an entity has been improved, restored, or updated through renovation work performed by another entity.
-
E.
redevelopedAfter
Indicates that one entity was redeveloped at a later time than, and as a subsequent phase or replacement to, 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_69ef841061e48190b5570f9562f7434d |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63b3337748190ae03ce1742a31d22 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:36 p.m.