Triple
T34040609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tipping Point |
E872931
|
entity |
| Predicate | eliminatesContestantsBetweenRounds |
P178166
|
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: [Tipping Point, eliminatesContestantsBetweenRounds, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eliminatesContestantsBetweenRounds Context triple: [Tipping Point, eliminatesContestantsBetweenRounds, yes]
-
A.
eliminatedInRound
Indicates that an entity was removed from further participation or competition during a specified round.
-
B.
eliminatedTeamsCount
Indicates the number of teams that have been removed from contention or disqualified in a given context or competition.
-
C.
loserElimination
Indicates that the entity identified as the loser in a competition, game, or contest is removed or disqualified from further participation.
-
D.
includedRound
Indicates that a particular round is part of, or contained within, a larger set, sequence, or event of rounds.
-
E.
teamEliminationMechanism
Indicates the method or rule by which a team is removed or knocked out from a competition or process.
- 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_69f349a3363081909cea4c9a848cefe2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70c53062c8190b4cb7be22ab00bc7 |
completed | May 3, 2026, 8:50 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70b94784c8190970d654e066eb50d |
completed | May 3, 2026, 8:47 a.m. |
Created at: May 1, 2026, 1:51 a.m.