Triple
T26394493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japanese Super Cup 2008 |
E663510
|
entity |
| Predicate | seasonOpeningMatchFor |
P23679
|
FINISHED |
| Object | Japanese football |
—
|
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: Japanese football | Statement: [Japanese Super Cup 2008, seasonOpeningMatchFor, Japanese football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonOpeningMatchFor Context triple: [Japanese Super Cup 2008, seasonOpeningMatchFor, Japanese football]
-
A.
openingMatch
chosen
Indicates that one entity serves as the initial or first match, game, or contest in a series, event, or competition involving another entity.
-
B.
hasOpeningMatchSeason
Indicates that an entity has a specific match designated as the opening match of a particular season.
-
C.
openingSeason
Indicates that an entity marks the beginning or first season of another entity, such as a series, event, or competition.
-
D.
seasonOpenerType
Indicates the specific type or category of a season-opening event or game associated with an entity.
-
E.
openingMatchResult
Indicates the outcome or result associated with the opening match in a series, tournament, 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_69ee883823988190b418b111be28a44a |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 26, 2026, 11:28 p.m.