Triple
T26623322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japanese Super Cup 2016 |
E668264
|
entity |
| Predicate | qualification1 |
P106510
|
FINISHED |
| Object | 2015 J1 League champions |
—
|
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: 2015 J1 League champions | Statement: [Japanese Super Cup 2016, qualification1, 2015 J1 League champions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: qualification1 Context triple: [Japanese Super Cup 2016, qualification1, 2015 J1 League champions]
-
A.
qualificationHeld
Indicates that an entity possesses or has obtained a particular qualification or credential.
-
B.
qualifyingFor
chosen
Indicates that one entity meets the necessary conditions or criteria to be eligible for another entity, status, or action.
-
C.
qualificationLevel
Indicates the degree or rank of competence, certification, or formal credentials required for or possessed in relation to something.
-
D.
hasQualification
Indicates that an entity possesses a specific qualification, credential, or competency.
-
E.
resultedInQualificationFor
Indicates that one event, action, or condition caused or led directly to an entity becoming eligible for a particular qualification, status, or credential.
- 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_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 2:22 a.m.