Triple
T4565142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ko’okiri Body Plunge |
E121889
|
entity |
| Predicate | hasOpeningContext |
P45798
|
FINISHED |
| Object | opened with Universal’s Volcano Bay |
—
|
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: opened with Universal’s Volcano Bay | Statement: [Ko’okiri Body Plunge, hasOpeningContext, opened with Universal’s Volcano Bay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpeningContext Context triple: [Ko’okiri Body Plunge, hasOpeningContext, opened with Universal’s Volcano Bay]
-
A.
hasOpeningDeclaredBy
Indicates that the opening or initial state of something is formally specified or announced by a particular agent or authority.
-
B.
hasOpeningType
Indicates that one entity has, features, or is characterized by a particular type or kind of opening.
-
C.
hasTextOpening
Indicates that an entity begins with or contains a specified initial segment of text.
-
D.
hasOpeningFeature
chosen
Indicates that an entity possesses a specific characteristic, element, or attribute related to its opening or entry point.
-
E.
isOpenTo
Indicates that one entity is receptive, willing, or available to consider, accept, or engage with another entity or proposal.
- 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_69bd463f156881908a99aca69c5721ac |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd589cde9081909b84186d700fc463 |
completed | March 20, 2026, 2:24 p.m. |
| PD | Predicate disambiguation | batch_69bd52254c648190a5144cfe8fa7e409 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:09 p.m.