Triple
T23970115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allu Ayaan |
E604204
|
entity |
| Predicate | publiclyAppearsOn |
P94492
|
FINISHED |
| Object | social media posts of Allu Arjun |
—
|
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: social media posts of Allu Arjun | Statement: [Allu Ayaan, publiclyAppearsOn, social media posts of Allu Arjun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publiclyAppearsOn Context triple: [Allu Ayaan, publiclyAppearsOn, social media posts of Allu Arjun]
-
A.
publiclyDisplayed
Indicates that something is shown or made visible in a public context or setting, accessible to people at large.
-
B.
mayAppearOn
chosen
Indicates that one entity is allowed or able to be shown, featured, or present on another entity (such as a platform, medium, or surface).
-
C.
appearsAs
Indicates that one entity is presented, perceived, or manifested in the form, role, or guise of another entity.
-
D.
appearsFor
Indicates that one entity is presented, shown, or made visible on behalf of, or in representation of, another entity.
-
E.
isRepresentedOn
Indicates that something serves as a visual, symbolic, or formal depiction of something else on a particular medium or surface.
- 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.