Triple
T32420518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Splash! |
E828445
|
entity |
| Predicate | hasAudienceVote |
P162575
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Splash!, hasAudienceVote, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAudienceVote Context triple: [Splash!, hasAudienceVote, true]
-
A.
hasPublicVoting
chosen
Indicates that decisions, selections, or evaluations are made through a voting process that is open and accessible to the general public.
-
B.
hasAudience
Indicates that an entity is intended to be received, viewed, or engaged with by a particular group of people.
-
C.
hadVoteIn
Indicates that an entity participated by casting a vote in a particular decision, election, or voting event.
-
D.
isAudienceChoiceFor
Indicates that one entity represents a choice, option, or selection available to an audience in relation to another entity.
-
E.
hasAudienceReception
Indicates the relationship between a work or event and how it is received, perceived, or evaluated by its audience.
- 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_69f3491b28bc8190b75cea7a507f337b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 1, 2026, 12:54 a.m.