Triple
T23969519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arya |
E604191
|
entity |
| Predicate | boostedStardomOf |
P104827
|
FINISHED |
| Object | Allu Arjun |
—
|
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: Allu Arjun | Statement: [Arya, boostedStardomOf, Allu Arjun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boostedStardomOf Context triple: [Arya, boostedStardomOf, Allu Arjun]
-
A.
basedOnStarPowerOf
Indicates that something is determined, influenced, or derived from the star power (e.g., fame, popularity, or celebrity status) of an entity.
-
B.
helpedBoostProminenceOf
chosen
Indicates that one entity contributed to increasing the visibility, recognition, or prominence of another entity.
-
C.
typicalBoost
Indicates a standard or commonly expected increase in magnitude, intensity, or effectiveness associated with something.
-
D.
strengthenedPowerIn
Indicates that one entity has increased, reinforced, or consolidated its power, influence, or control within a particular context, domain, or location represented by the other entity.
-
E.
boosterRole
Indicates that an entity serves in a supporting or enhancing capacity to strengthen, amplify, or promote another entity’s function, status, or effect.
- 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_69e29543019c8190872462e593cc50b4 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d1db392c8190a1044b75b898243a |
completed | April 29, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:25 p.m.