Triple
T20412210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vanara |
E500612
|
entity |
| Predicate | associatedEpicEvent |
P140044
|
FINISHED |
| Object | war against Ravana |
—
|
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: war against Ravana | Statement: [Vanara, associatedEpicEvent, war against Ravana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedEpicEvent Context triple: [Vanara, associatedEpicEvent, war against Ravana]
-
A.
closelyAssociatedEvent
Indicates that one event is strongly related to, connected with, or occurs in close conjunction with another event.
-
B.
associatedWithAncientEvent
Indicates a relationship where an entity is connected or related in some way to a specific ancient historical event.
-
C.
associatedEpicHero
Indicates a relationship where one entity is linked to, or thematically connected with, a particular epic hero.
-
D.
historicalEntityAssociated
Indicates that one entity has a documented historical connection, relevance, or involvement with another entity.
-
E.
historicalMovementAssociatedWith
Indicates that there is an association between an entity and a historical movement, such as a social, political, cultural, or ideological current in history.
- 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_69e0b4a935588190b9446a99b37ced44 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67a3f8fdc8190b05b6c41b38f34b7 |
completed | April 20, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
| PDg | Predicate description generation | batch_69e58d7481508190a87c8b88f9df9879 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:30 a.m.