Triple
T26623325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japanese Super Cup 2016 |
E668264
|
entity |
| Predicate | team2Qualification |
P3203
|
FINISHED |
| Object | 2015 Emperor's Cup winners |
—
|
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: 2015 Emperor's Cup winners | Statement: [Japanese Super Cup 2016, team2Qualification, 2015 Emperor's Cup winners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: team2Qualification Context triple: [Japanese Super Cup 2016, team2Qualification, 2015 Emperor's Cup winners]
-
A.
team2State
Indicates the current status or condition of the second team in a given context or event.
-
B.
tournamentTeams
Indicates that certain teams are participants in a particular tournament.
-
C.
team2
chosen
Indicates that the second team involved in a competitive or collaborative context is associated with a given entity or event.
-
D.
conferenceTeam1
Indicates that an entity participates in or is associated with the first team in a conference-related context.
-
E.
team2Wins
Indicates that the second team is the winner in a given game, match, or competition.
- 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_69ee9cff507c819092b95bf7219a702e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f615e75cac8190972274bf5552a6d4 |
completed | May 2, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 2:22 a.m.