Triple
T32478104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falaknuma Palace |
E830032
|
entity |
| Predicate | reopeningAsHotel |
P63192
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [Falaknuma Palace, reopeningAsHotel, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reopeningAsHotel Context triple: [Falaknuma Palace, reopeningAsHotel, 2010]
-
A.
reopeningAs
chosen
Indicates that an entity that was previously closed or inactive is starting operations again under a new or updated form, identity, or function.
-
B.
closedAsHotel
Indicates that an establishment ceased operating in general and specifically stopped functioning as a hotel.
-
C.
reopeningToPublic
Indicates that an entity, previously closed or restricted, is being opened again for access or use by the general public.
-
D.
reopeningDate
Indicates the date on which something that was previously closed is opened again for use or access.
-
E.
reopeningEvent
Indicates an event in which something that was previously closed, suspended, or inactive is opened or made operational again.
- 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_69f3491ff3b48190b50a7fa00bb05b1f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c3933b248190afb0b42934171ef9 |
completed | May 3, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:58 a.m.