Triple
T36125896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blackout (game show) |
E1044878
|
entity |
| Predicate | contestantTeams |
P189752
|
FINISHED |
| Object | civilian contestants paired with celebrities |
—
|
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: civilian contestants paired with celebrities | Statement: [Blackout (game show), contestantTeams, civilian contestants paired with celebrities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contestantTeams Context triple: [Blackout (game show), contestantTeams, civilian contestants paired with celebrities]
-
A.
tournamentTeams
Indicates that certain teams are participants in a particular tournament.
-
B.
coreTeams
Indicates that the entities are part of the same primary or central team within an organization or project.
-
C.
teamsRepresent
Indicates that one or more teams act on behalf of, or serve as the official representatives of, a particular entity, organization, or group.
-
D.
conferenceTeam1
Indicates that an entity participates in or is associated with the first team in a conference-related context.
-
E.
eligibleTeamsFrom
Indicates that certain teams qualify or are allowed to originate from a specified source, context, or selection criteria.
- 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_69f76e356c908190abc6ca1e6a05b011 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fbca6c066c8190a1599202f341417f |
completed | May 6, 2026, 11:10 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fbc9d0854c8190aa00093274afebb8 |
completed | May 6, 2026, 11:08 p.m. |
Created at: May 3, 2026, 4:08 p.m.