Triple
T26150378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Power Star |
E659796
|
entity |
| Predicate | usedInFanClubsOf |
P150794
|
FINISHED |
| Object | Pawan Kalyan |
—
|
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: Pawan Kalyan | Statement: [Power Star, usedInFanClubsOf, Pawan Kalyan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInFanClubsOf Context triple: [Power Star, usedInFanClubsOf, Pawan Kalyan]
-
A.
hasFanBaseFor
chosen
Indicates that an entity has a group of supporters or admirers specifically dedicated to another entity (such as a work, person, or brand).
-
B.
hasFanBaseDepictedAs
Indicates that an entity has a fan base that is visually or narratively represented in some form (e.g., in media, artwork, or documentation).
-
C.
hasFanBaseFrom
Indicates that an entity has a significant group of supporters or followers originating from a specified place, group, or source.
-
D.
fanDestination
Indicates that one entity is the intended target or recipient of another entity’s enthusiasm, admiration, or fandom.
-
E.
fanOwned
Indicates that the entity is owned or controlled by fans, typically through collective or community-based ownership rather than traditional private or corporate ownership.
- 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_69ee5bc496a88190af7deb7ab5e081de |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 26, 2026, 8:24 p.m.