Triple
T5871609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyota Cup |
E130528
|
entity |
| Predicate | roleInFootball |
P24689
|
FINISHED |
| Object | unofficial world club 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: unofficial world club championship | Statement: [Toyota Cup, roleInFootball, unofficial world club championship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInFootball Context triple: [Toyota Cup, roleInFootball, unofficial world club championship]
-
A.
roleInRugby
Indicates the specific position or function an entity holds within the context of playing or participating in rugby.
-
B.
associatedPlayerRole
Indicates a relationship where a specific role or function is linked to, or held by, a particular player.
-
C.
roleInManchesterCity
Indicates that an entity holds or has held a specific role or position within Manchester City Football Club.
-
D.
roleAtSportsTeam
Indicates the specific position or function an individual holds within a sports team.
-
E.
typeOfFootball
chosen
Indicates the specific code or variant of football that characterizes or classifies a given football-related entity.
- 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_69c0085047dc8190af24e311edad3c07 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0432fea5881909f5c291dd8db6105 |
completed | March 22, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69c033499ca08190bd26cee5b03f6306 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:56 p.m.