Triple
T20005018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toheeb Jimoh |
E494430
|
entity |
| Predicate | notableCharacterSport |
P138325
|
FINISHED |
| Object | association 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: association football | Statement: [Toheeb Jimoh, notableCharacterSport, association football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCharacterSport Context triple: [Toheeb Jimoh, notableCharacterSport, association football]
-
A.
notableAthlete
Indicates that the subject is a well-known or distinguished athlete associated with the object (such as a sport, team, or organization).
-
B.
notableAthleteFrom
Indicates that an athlete is notably associated with or originates from a particular place or region.
-
C.
knownForSports
Indicates that an entity is recognized or notable for its involvement, achievement, or association with sports.
-
D.
notableSportIncluded
Indicates that a particular sport is prominently featured or included as a notable component within something, such as an event, program, or context.
-
E.
hasNotablePlayer
Indicates that an entity (such as a team or club) is associated with a player who is particularly distinguished, famous, or significant in its context.
- F. None of above. chosen
Provenance (4 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e661a46c748190a141ab5aac6ea250 |
completed | April 20, 2026, 5:25 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc20888819083c9118a09d0d2dc |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 3:33 p.m.