Triple
T3088645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | For the First Time in Forever: A Frozen Sing-Along Celebration |
E64433
|
entity |
| Predicate | hasAudienceParticipation |
P45833
|
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: [For the First Time in Forever: A Frozen Sing-Along Celebration, hasAudienceParticipation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAudienceParticipation Context triple: [For the First Time in Forever: A Frozen Sing-Along Celebration, hasAudienceParticipation, yes]
-
A.
hasAudienceReception
Indicates the relationship between a work or event and how it is received, perceived, or evaluated by its audience.
-
B.
hasAudience
Indicates that an entity is intended to be received, viewed, or engaged with by a particular group of people.
-
C.
hasAudienceSize
Indicates the relationship between an entity and the number of people or size of group that receives, views, or engages with it.
-
D.
hasParticipants
Indicates that an event, activity, or situation involves one or more entities as participants in it.
-
E.
hasAuditorium
Indicates that one entity possesses or includes an auditorium as part of its facilities.
- 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_69ad857c97d88190b26f9b1c90839c77 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada20b99a4819090c3d3e08ed556ad |
completed | March 8, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69ad9ded78f881908be6fc0fb7c35764 |
completed | March 8, 2026, 4:03 p.m. |
| PDg | Predicate description generation | batch_69ada0f6fef48190b13898be383a246b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:03 p.m.