Triple
T15793719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hilton Moscow Leningradskaya |
E382921
|
entity |
| Predicate | hotelReopeningDate |
P10067
|
FINISHED |
| Object | 2008 |
—
|
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: 2008 | Statement: [Hilton Moscow Leningradskaya, hotelReopeningDate, 2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hotelReopeningDate Context triple: [Hilton Moscow Leningradskaya, hotelReopeningDate, 2008]
-
A.
reopeningDate
chosen
Indicates the date on which something that was previously closed is opened again for use or access.
-
B.
partialReopeningDate
Indicates the date on which an entity is reopened in a limited or partial capacity, rather than fully resuming normal operation.
-
C.
plannedOpeningDate
Indicates the date on which something is scheduled or intended to begin operating or become available.
-
D.
officialOpeningDate
Indicates the calendar date on which something is formally inaugurated or officially opened for use or operation.
-
E.
rerAOpeningDate
Indicates the date on which something (such as a facility, service, or route) is opened again after having been closed.
- 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4db55308190875a04f982c44cea |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e00537bd1c81908d6e832792fd934f |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:48 a.m.