Triple
T8791949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wild Card Game |
E209186
|
entity |
| Predicate | advancingTeam |
P6987
|
FINISHED |
| Object | winner of the Wild Card Game |
—
|
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: winner of the Wild Card Game | Statement: [Wild Card Game, advancingTeam, winner of the Wild Card Game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: advancingTeam Context triple: [Wild Card Game, advancingTeam, winner of the Wild Card Game]
-
A.
advancesTeamsTo
chosen
Indicates that one entity causes or marks the progression of one or more teams to a subsequent stage, level, or round in a process or competition.
-
B.
managedTeam
Indicates that one entity had responsibility for directing, supervising, and coordinating the work of another group or team.
-
C.
teamAction
Indicates an action that is performed collectively by a group functioning as a team.
-
D.
advancesNumberOfTeams
Indicates that one entity causes an increase in how many teams progress or move forward in a given context.
-
E.
ledTeamTo
Indicates that one entity acted as a leader or guiding force that directed a team toward achieving a particular goal, outcome, or success.
- 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_69ca836240888190a62b262e56a69d2f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f8e6e4881909155c40c52bc082c |
completed | March 31, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1d48f08190b325a77d4c76d223 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:43 p.m.