Triple
T33405696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rover (Carousel of Progress) |
E855431
|
entity |
| Predicate | previouslyAppearedInPark |
P91122
|
FINISHED |
| Object | Disneyland |
—
|
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 | Statement: [Rover (Carousel of Progress), previouslyAppearedInPark, Disneyland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previouslyAppearedInPark Context triple: [Rover (Carousel of Progress), previouslyAppearedInPark, Disneyland]
-
A.
debutedInPark
chosen
Indicates that an entity made its first public appearance or introduction within a specific park.
-
B.
introducedInPark
Indicates that one entity caused two or more entities to meet or become acquainted with each other while they were in a park.
-
C.
openedInPark
Indicates that an entity was opened, inaugurated, or began operating within the boundaries of a park.
-
D.
firstInPark
Indicates that one entity is the earliest or first to arrive, appear, or be present in a specified park relative to other entities.
-
E.
hasFormerAmusementParkSite
Indicates that a location or entity currently occupies or includes the site where an amusement park once existed.
- 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fefa064ab48190925759950d0d94d9 |
completed | May 9, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69fef96ae5d08190b027435753c44821 |
completed | May 9, 2026, 9:07 a.m. |
Created at: May 1, 2026, 1:36 a.m.