Triple
T26579985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Star Wars: Hyperspace Mountain |
E667049
|
entity |
| Predicate | firstIntroducedAt |
P18472
|
FINISHED |
| Object | Disneyland Park (California) |
—
|
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: Disneyland Park (California) | Statement: [Star Wars: Hyperspace Mountain, firstIntroducedAt, Disneyland Park (California)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstIntroducedAt Context triple: [Star Wars: Hyperspace Mountain, firstIntroducedAt, Disneyland Park (California)]
-
A.
introducedInYear
Indicates the year in which something was first introduced, launched, or made available.
-
B.
firstAppearedAt
chosen
Indicates the point in time or specific event at which an entity was first introduced, observed, or became known.
-
C.
introducedFrom
Indicates that one entity was brought, originated, or caused to appear in a context, system, or environment by another entity.
-
D.
reintroducedInYear
Indicates that an entity, previously absent or discontinued, was brought back or reinstated in a specified year.
-
E.
firstUsedOn
Indicates the date, time, or context in which something was initially applied, activated, or put into use on a particular object or entity.
- 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_69ee9cfb7e548190b60a9031182f5a7e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69fe831c97c88190b27ecf100e25c2a0 |
completed | May 9, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_69fe7f1b92648190b14e56bcaee5d0ca |
completed | May 9, 2026, 12:26 a.m. |
Created at: April 27, 2026, 2:02 a.m.