Triple
T17979350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raghava |
E449558
|
entity |
| Predicate | roleHighlights |
P11527
|
FINISHED |
| Object | central hero of the Ramayana |
—
|
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: central hero of the Ramayana | Statement: [Raghava, roleHighlights, central hero of the Ramayana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleHighlights Context triple: [Raghava, roleHighlights, central hero of the Ramayana]
-
A.
highlightsRole
Indicates that one entity emphasizes, showcases, or draws special attention to the role or function of another entity.
-
B.
roleCharacteristic
Indicates that a particular characteristic, quality, or attribute is associated with and helps define a given role or function.
-
C.
socialRoleEmphasis
Indicates an emphasis on or prioritization of a particular social role within a relationship or interaction.
-
D.
portfolioRole
Indicates the specific function, capacity, or position an entity holds within a portfolio or collection of assets.
-
E.
roleInText
chosen
Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, character).
- 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b201d1508190a9d6abbfd04bdcae |
completed | April 19, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_69e3f8fa62688190a5d5c361ab896256 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:22 a.m.