Triple
T2390081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SeaWorld San Diego |
E48919
|
entity |
| Predicate | hasShowType |
P15144
|
FINISHED |
| Object | animal presentations |
—
|
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: animal presentations | Statement: [SeaWorld San Diego, hasShowType, animal presentations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShowType Context triple: [SeaWorld San Diego, hasShowType, animal presentations]
-
A.
showType
chosen
Indicates the category or format in which something is presented or displayed (e.g., type of show, presentation, or display mode).
-
B.
hasDisplayType
Indicates the type or category of display associated with an entity, such as the format, mode, or presentation style used to show its content.
-
C.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
D.
hasPresenterType
Indicates the specific role or category of presenter associated with an event, item, or presentation.
-
E.
hasCurrentType
Indicates that an entity currently possesses or is classified under a specific type or category, as opposed to past or potential types.
- 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_69a88aa5f63081908d07fd302029fcbd |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc7de1478819082238e8b8f88ed06 |
completed | March 7, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69abc5a1b5748190b4cd8989700f4dd2 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.