Triple
T19925730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Virata |
E478917
|
entity |
| Predicate | epicTradition |
P2989
|
FINISHED |
| Object | Itihasa |
—
|
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: Itihasa | Statement: [Kingdom of Virata, epicTradition, Itihasa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: epicTradition Context triple: [Kingdom of Virata, epicTradition, Itihasa]
-
A.
epic
Indicates that an entity is characterized as grand, heroic, or extraordinarily impressive in scale, style, or impact.
-
B.
nationalEpic
Indicates that one work is regarded as the principal epic narrative representing the history, culture, or identity of a nation.
-
C.
sagaTradition
Indicates that something belongs to, derives from, or is characteristic of a saga-based narrative or cultural tradition.
-
D.
eraOfMyth
Indicates a temporal relationship where an event, story, or phenomenon belongs to or takes place during a mythological or legendary era.
-
E.
literaryTradition
chosen
Indicates a relationship where a work, practice, or expression belongs to, arises from, or participates in a particular established body of literary customs, styles, or conventions.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e659c992fc8190bd262d528be0e636 |
completed | April 20, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69e537f070b481908958e0e5911dcdc1 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.