Triple
T7006001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tohoku Rakuten Golden Eagles |
E162457
|
entity |
| Predicate | leagueChampionship |
P2689
|
FINISHED |
| Object | 2013 Pacific League championship |
—
|
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: 2013 Pacific League championship | Statement: [Tohoku Rakuten Golden Eagles, leagueChampionship, 2013 Pacific League championship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leagueChampionship Context triple: [Tohoku Rakuten Golden Eagles, leagueChampionship, 2013 Pacific League championship]
-
A.
championshipLeague
Indicates that an entity is a championship-level competition or league in which teams or individuals compete for a title.
-
B.
championLeague
chosen
Indicates that an entity has won or holds the championship title in a particular league or competitive event.
-
C.
leagueCup
Indicates that an entity is a cup-style competition organized within or by a specific league.
-
D.
leagueChampionships
Indicates the number of league championship titles an entity has won.
-
E.
leagueOrCup
Indicates that one entity is a league or cup competition in which the other entity participates or is associated.
- 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_69c6885928148190ae31909fbb5e9849 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dc34b5a88190a793e07dd4d0018b |
completed | March 27, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c67c94819084fdcf0398606027 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:33 p.m.