Triple
T26150364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Power Star |
E659796
|
entity |
| Predicate | indicatesPopularity |
P1755
|
FINISHED |
| Object | massive fan following |
—
|
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: massive fan following | Statement: [Power Star, indicatesPopularity, massive fan following]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indicatesPopularity Context triple: [Power Star, indicatesPopularity, massive fan following]
-
A.
peakPopularity
Indicates the time or context in which something reaches its highest level of popularity relative to other times or contexts.
-
B.
popularity
chosen
Indicates how widely liked, admired, or favored something or someone is by a group of people.
-
C.
hasPopularityCharacteristic
Indicates that an entity possesses a particular attribute or quality related to its level or type of popularity.
-
D.
isPopularAs
Indicates that an entity is widely liked, well-known, or favored in a particular role, context, or capacity.
-
E.
hasPopularityInfluencedBy
Indicates that the popularity level of one entity is affected or shaped by another specified factor or 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_69ee5bc496a88190af7deb7ab5e081de |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69f60c0a164c819098ef0266d84c3bdf |
completed | May 2, 2026, 2:36 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 8:24 p.m.