Triple
T26733085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rivers of America |
E674026
|
entity |
| Predicate | openingDateForLocation |
P10845
|
FINISHED |
| Object | 1983-04-15 at Tokyo Disneyland |
—
|
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: 1983-04-15 at Tokyo Disneyland | Statement: [Rivers of America, openingDateForLocation, 1983-04-15 at Tokyo Disneyland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingDateForLocation Context triple: [Rivers of America, openingDateForLocation, 1983-04-15 at Tokyo Disneyland]
-
A.
officialOpeningDate
chosen
Indicates the calendar date on which something is formally inaugurated or officially opened for use or operation.
-
B.
firstLocationOpeningDate
Indicates the date on which the first location associated with the subject entity was opened.
-
C.
openingTime
Indicates the time at which a place, service, or event begins operating or becomes accessible.
-
D.
expansionOpeningDate
Indicates the date on which an expansion of something (such as a facility, service, or project) was officially opened or became operational.
-
E.
plannedOpeningDate
Indicates the date on which something is scheduled or intended to begin operating or become available.
- 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_69eecda57ab481909424e98f2835e7d8 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6383625cc8190aa223d8ef655743c |
completed | May 2, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 3:46 a.m.