Triple
T9928049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuks |
E187971
|
entity |
| Predicate | isPopularAmong |
P729
|
FINISHED |
| Object | South African university sports fans |
—
|
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: South African university sports fans | Statement: [Tuks, isPopularAmong, South African university sports fans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPopularAmong Context triple: [Tuks, isPopularAmong, South African university sports fans]
-
A.
isPopularWith
chosen
Indicates that one entity is well-liked, favored, or widely accepted by another entity or group.
-
B.
isPopularOnSocialMedia
Indicates that an entity is widely followed, frequently engaged with, or broadly recognized across social media platforms.
-
C.
hasPopularityInfluencedBy
Indicates that the popularity level of one entity is affected or shaped by another specified factor or entity.
-
D.
popularity
Indicates how widely liked, admired, or favored something or someone is by a group of people.
-
E.
popularizedIn
Indicates that something became widely known, accepted, or fashionable within a particular place, time period, or context.
- 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_69ca82b22a688190b52c75bd48429c10 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cdb59d7ad08190982a1584547190bd |
completed | April 2, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69cd1d90b8a8819081748f129c0c6ab6 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:43 p.m.