Triple
T29476994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Bowl XLVII halftime show |
E747675
|
entity |
| Predicate | reunionOf |
P147224
|
FINISHED |
| Object | Destiny's Child |
—
|
NE NERFINISHED |
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: Destiny's Child | Statement: [Super Bowl XLVII halftime show, reunionOf, Destiny's Child]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reunionOf Context triple: [Super Bowl XLVII halftime show, reunionOf, Destiny's Child]
-
A.
reunionWith
chosen
Indicates that two or more entities come back together after a period of separation or absence.
-
B.
reunionOfAllMembers
Indicates that a gathering or event involves the complete set of members, with no one from the defined group absent.
-
C.
reunionType
Indicates the specific kind or category of reunion event that relates the involved entities.
-
D.
reunionContext
Indicates the situational setting, circumstances, or background in which a reunion between entities takes place.
-
E.
reunitedFor
Indicates that entities who were previously separated have come back together or been brought back into association.
- 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_69f0bd42cf308190bb01b20bc5b7c2d0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66bd57cac81909e92d58fb91b4a5c |
completed | May 2, 2026, 9:25 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 4:01 p.m.