Triple
T22855761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revel Atlantic City |
E566474
|
entity |
| Predicate | officialGrandOpeningDate |
P10845
|
FINISHED |
| Object | May 25, 2012 |
—
|
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: May 25, 2012 | Statement: [Revel Atlantic City, officialGrandOpeningDate, May 25, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialGrandOpeningDate Context triple: [Revel Atlantic City, officialGrandOpeningDate, May 25, 2012]
-
A.
officialOpeningDate
chosen
Indicates the calendar date on which something is formally inaugurated or officially opened for use or operation.
-
B.
plannedOpeningDate
Indicates the date on which something is scheduled or intended to begin operating or become available.
-
C.
reopeningDate
Indicates the date on which something that was previously closed is opened again for use or access.
-
D.
openingDay
Indicates the specific day on which something, typically an event, season, or venue, officially begins or first opens to the public.
-
E.
officialOpeningYear
Indicates the calendar year in which something was formally opened or inaugurated for official use.
- 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_69e2458750b481908a8e4cf4609cc6cf |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17ebc6a088190890f2474f18a10eb |
completed | April 29, 2026, 3:45 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:37 p.m.