Triple
T22915419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fujisankei Classic |
E568721
|
entity |
| Predicate | notablePastChampion |
P28766
|
FINISHED |
| Object | Isao Aoki |
—
|
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: Isao Aoki | Statement: [Fujisankei Classic, notablePastChampion, Isao Aoki]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePastChampion Context triple: [Fujisankei Classic, notablePastChampion, Isao Aoki]
-
A.
notableFormerChampion
chosen
Indicates that an entity was once a champion of something and is recognized as particularly distinguished or prominent in that former champion role.
-
B.
notableEarlyWinner
Indicates that an entity is recognized for having achieved a significant win or success earlier than most others in a given context or competition.
-
C.
notableFirstWinner
Indicates that the subject is the first and notably recognized winner of the object (such as an award, competition, or title).
-
D.
menPastChampion
Indicates that the subject was a past champion in a men's competition or event.
-
E.
notableWinner
Indicates that the subject is a particularly distinguished or prominent winner of the referenced competition, award, or contest.
- 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_69e2458d90c88190a58cead4e781ca6a |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18079217481908db98882929ac69a |
completed | April 29, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69ef3b7c5fc081909ac50c5c8569cc19 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:42 p.m.