Triple
T36834682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Entertainment City |
E910237
|
entity |
| Predicate | secondIntegratedResortOpened |
P200219
|
FINISHED |
| Object | City of Dreams Manila |
—
|
NE NERFINISHED |
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: City of Dreams Manila | Statement: [Entertainment City, secondIntegratedResortOpened, City of Dreams Manila]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondIntegratedResortOpened Context triple: [Entertainment City, secondIntegratedResortOpened, City of Dreams Manila]
-
A.
casinoOpeningDate
Indicates the calendar date on which a casino first began operating or officially opened to the public.
-
B.
thirdBuildingOpened
Indicates that the third building in a sequence or group has been officially opened or made operational.
-
C.
openedAsResort
Indicates that something began operating or was first established in the capacity of a resort.
-
D.
secondTheatreOpened
Indicates that an entity opened its second theatre location or venue.
-
E.
hasSisterResort
Indicates that one resort is formally associated with another as its sister property, typically under common ownership or branding.
- F. None of above. chosen
Provenance (4 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_69f76e7e9d60819092442fba73290a46 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff7ae5d088819089aa3b6360b6b749 |
completed | May 9, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69ff7a4df6488190bf60d675b36b1d6d |
completed | May 9, 2026, 6:17 p.m. |
| PDg | Predicate description generation | batch_69ff7ae4bc948190a4cd21a60d091977 |
completed | May 9, 2026, 6:20 p.m. |
Created at: May 3, 2026, 4:13 p.m.