Triple
T36605299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Be Our Guest Restaurant |
E903028
|
entity |
| Predicate | softOpenedOn |
P23302
|
FINISHED |
| Object | 2012-11-19 |
—
|
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: 2012-11-19 | Statement: [Be Our Guest Restaurant, softOpenedOn, 2012-11-19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: softOpenedOn Context triple: [Be Our Guest Restaurant, softOpenedOn, 2012-11-19]
-
A.
softOpeningDate
chosen
Indicates the date on which a business, venue, or service begins limited or trial operations before its official grand opening.
-
B.
openedFrom
Indicates that one entity was initiated, accessed, or launched as a result of an action performed within another entity.
-
C.
softOpeningPeriod
Indicates a time-limited initial phase during which an operation or service is partially or informally open before its full official launch.
-
D.
softOpeningYear
Indicates the year in which an entity began limited or preliminary operations before its official full opening.
-
E.
openedIn
Indicates that an entity (such as a business, event, or institution) began operating or was inaugurated in a specific time period or location.
- 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_69f76e66b7b88190848f7a3e1188915f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c33f442c81908300da6a1631180a |
completed | May 3, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69f7c1bbf5848190a698fdbec307886a |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.