Triple
T20106078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Water features at Universal CityWalk |
E490181
|
entity |
| Predicate | typicalShowElements |
P138713
|
FINISHED |
| Object | synchronized water jets |
—
|
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: synchronized water jets | Statement: [Water features at Universal CityWalk, typicalShowElements, synchronized water jets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalShowElements Context triple: [Water features at Universal CityWalk, typicalShowElements, synchronized water jets]
-
A.
showElement
Indicates that one entity causes a specific element or component to be displayed or made visible to another entity or within a given context.
-
B.
showsThat
Indicates that one entity demonstrates, proves, or provides evidence for the truth or validity of another.
-
C.
showType
Indicates the category or format in which something is presented or displayed (e.g., type of show, presentation, or display mode).
-
D.
relatedShowElement
Indicates that one show element is associated with or connected to another show element in some relevant way.
-
E.
includesShow
Indicates that one entity contains or features a particular show as part of its content or offerings.
- F. None of above. chosen
Provenance (4 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_69da62636cc08190982cc71733a17b8d |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e666dbad30819082454f360f358131 |
completed | April 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69e54cf788188190a46cc49c9ce7617f |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc2bc3c819088c33cd263303433 |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 11:28 p.m.