Triple
T28161943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luhya |
E714917
|
entity |
| Predicate | notableFootballClubSupport |
P101177
|
FINISHED |
| Object | AFC Leopards |
—
|
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: AFC Leopards | Statement: [Luhya, notableFootballClubSupport, AFC Leopards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFootballClubSupport Context triple: [Luhya, notableFootballClubSupport, AFC Leopards]
-
A.
supportsLeagueClub
Indicates that one entity provides backing, assistance, or endorsement to a league-affiliated club.
-
B.
associationFootballClub
Indicates that the subject is an association football (soccer) club, i.e., an organized team entity that plays the sport of association football.
-
C.
clubFoundedSupported
Indicates that an entity (such as a person, organization, or group) played a role in founding a club and/or providing support for its establishment or ongoing activities.
-
D.
associationFootballClubIn
Indicates that an association football (soccer) club is located in or based in a specified place or region.
-
E.
supportedClub
chosen
Indicates that one entity has given their backing, endorsement, or assistance to a particular club.
- 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_69efd6b156448190bfa15958208395c3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_6a0091ad8b8c8190b0f00a3358e59bc1 |
completed | May 10, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_6a008f2813ec81909a54c2dfa5c75dc7 |
completed | May 10, 2026, 1:59 p.m. |
Created at: April 27, 2026, 10:07 p.m.