Triple
T20828762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delfinario de Varadero |
E512770
|
entity |
| Predicate | hasShowElement |
P43274
|
FINISHED |
| Object | acrobatic dolphin jumps |
—
|
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: acrobatic dolphin jumps | Statement: [Delfinario de Varadero, hasShowElement, acrobatic dolphin jumps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShowElement Context triple: [Delfinario de Varadero, hasShowElement, acrobatic dolphin jumps]
-
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.
hasExhibitElement
chosen
Indicates that something (such as an exhibit or display) includes or is composed of a particular element or component.
-
C.
hasShowUse
Indicates that something is used or presented as an example or demonstration in a show, display, or illustrative context.
-
D.
hasLayoutElement
Indicates that one entity includes, contains, or is associated with a specific layout element as part of its structural or visual arrangement.
-
E.
hasView
Indicates that one entity provides a visual perspective or outlook onto another entity or scene.
- 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_69e0b4ce39108190a6e8e5df4f1c8dc5 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c31e387481909fcf323f97019803 |
completed | April 21, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a1f4f48190aa9fb4ef8f8aea5a |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:42 p.m.