Triple
T10476570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adikavi Pampa |
E247057
|
entity |
| Predicate | portraysInVikramarjunaVijaya |
P94240
|
FINISHED |
| Object | Arjuna as hero |
—
|
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: Arjuna as hero | Statement: [Adikavi Pampa, portraysInVikramarjunaVijaya, Arjuna as hero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portraysInVikramarjunaVijaya Context triple: [Adikavi Pampa, portraysInVikramarjunaVijaya, Arjuna as hero]
-
A.
portrayalOfGungaDin
Indicates that one entity is a depiction, representation, or performance of the character Gunga Din.
-
B.
portraysPurushaAs
Indicates that one entity represents or depicts another entity as Purusha, the cosmic or primordial being.
-
C.
inRamayana
Indicates that the subject participates in, appears within, or is otherwise part of the events or narrative of the Ramayana.
-
D.
viewOnMahabharata
Indicates a stance, interpretation, or perspective that someone holds regarding the Mahabharata.
-
E.
hasPositionInMahabharata
Indicates that one entity holds or is assigned a specific role, rank, or position within the context of the Mahabharata narrative.
- F. None of above. chosen
Provenance (4 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_69d381c16c248190a2fe5b471e584e9c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5095021e081908dfaa467938c13fd |
completed | April 7, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69d4fb84bafc8190819757b93620508a |
completed | April 7, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69d4fe058fcc81909428137d9ffd6d90 |
completed | April 7, 2026, 12:52 p.m. |
Created at: April 6, 2026, 12:21 p.m.