Triple
T26752615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SpongeBob’s Splash Bash |
E674581
|
entity |
| Predicate | hasInteractivity |
P27769
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [SpongeBob’s Splash Bash, hasInteractivity, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInteractivity Context triple: [SpongeBob’s Splash Bash, hasInteractivity, yes]
-
A.
hasInteractiveActivity
chosen
Indicates that an entity includes or is associated with an activity that requires active user participation or engagement.
-
B.
hasInteraction
Indicates that there is some form of interaction or mutual action occurring between the related entities.
-
C.
hasInteractionMode
Indicates the way in which two entities engage or interact with each other, specifying the manner, channel, or pattern of their interaction.
-
D.
hasInteractiveTechnology
Indicates that an entity is equipped with or incorporates technology enabling user interaction or responsive engagement.
-
E.
supportsInteractiveWidgets
Indicates that an entity is capable of handling or enabling interactive widgets within its context or environment.
- 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_69eecda6e9dc81908452fab3ba17ed9b |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: April 27, 2026, 3:54 a.m.