Triple
T9576755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Seas with Nemo & Friends |
E231063
|
entity |
| Predicate | hasSoftOpeningYear |
P23302
|
FINISHED |
| Object | 2006 |
—
|
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: 2006 | Statement: [The Seas with Nemo & Friends, hasSoftOpeningYear, 2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSoftOpeningYear Context triple: [The Seas with Nemo & Friends, hasSoftOpeningYear, 2006]
-
A.
officialOpeningYear
Indicates the calendar year in which something was formally opened or inaugurated for official use.
-
B.
originalPlannedOpeningYear
Indicates the year that was initially scheduled or intended for something to open, before any delays or changes.
-
C.
softOpeningDate
chosen
Indicates the date on which a business, venue, or service begins limited or trial operations before its official grand opening.
-
D.
hasOpening
Indicates that one entity possesses or features an opening, gap, or entrance that allows access, passage, or exposure.
-
E.
openedAt
Indicates that an entity began operating, became accessible, or was first made available at a specific time or date.
- 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_69ca848091c48190bc313d6620d09555 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd99ac17a48190bb8448394f22b1e9 |
completed | April 1, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69ccd59fd7408190b36831902e3f37f7 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:05 p.m.