Triple
T25235199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amarendra Baahubali |
E632317
|
entity |
| Predicate | leadsBattle |
P18835
|
FINISHED |
| Object | war against Kalakeya tribe |
—
|
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 Kalakeya tribe | Statement: [Amarendra Baahubali, leadsBattle, war against Kalakeya tribe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadsBattle Context triple: [Amarendra Baahubali, leadsBattle, war against Kalakeya tribe]
-
A.
featuresBattle
Indicates that one entity includes, presents, or involves a battle as a significant element or event.
-
B.
battleOpponent
chosen
Indicates that two entities are engaged in or designated as opponents in a battle or combat scenario.
-
C.
mainBattle
Indicates that one battle is the primary or most significant engagement associated with a particular conflict, campaign, or entity.
-
D.
followedBattle
Indicates that one battle occurred after and as a consequence or continuation of another battle.
-
E.
keyBattleEvent
Indicates that the event represents a major or decisive moment within a battle or conflict.
- 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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f47df84cf0819089ea6c07d67b9f01 |
completed | May 1, 2026, 10:18 a.m. |
| PD | Predicate disambiguation | batch_69f44d849e7c81909945438f40e35362 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 1:06 p.m.