Triple
T23389532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jungle Cruise |
E593973
|
entity |
| Predicate | statusAtHongKongDisneyland |
P20989
|
FINISHED |
| Object | operating |
—
|
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: operating | Statement: [Jungle Cruise, statusAtHongKongDisneyland, operating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAtHongKongDisneyland Context triple: [Jungle Cruise, statusAtHongKongDisneyland, operating]
-
A.
visitorAttractionStatus
chosen
Indicates the current operational or accessibility status of a visitor attraction (e.g., open, closed, restricted).
-
B.
openingDateAtHong Kong Disneyland
Indicates the date on which Hong Kong Disneyland officially opened.
-
C.
closingDateAtTokyoDisneyland
Indicates the date on which something (such as an attraction, event, or facility) stops operating or ends at Tokyo Disneyland.
-
D.
closingDateAtWaltDisneyStudiosPark
Indicates the date on which something (typically an attraction or feature) ceased operations specifically at Walt Disney Studios Park.
-
E.
themeParkPresence
Indicates that an entity is present at, located in, or associated with a theme park in the context of a given event or situation.
- 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_69e25d2754fc819085deea939bde60ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a49a7c14819082aab826715976c5 |
completed | April 29, 2026, 6:26 a.m. |
| PD | Predicate disambiguation | batch_69f061dde2e481908308952f9c0d3c2e |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:35 p.m.