Triple
T29212577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Padayappa |
E740581
|
entity |
| Predicate | featuresIconicConfrontationBetween |
P90892
|
FINISHED |
| Object | Padayappa and Neelambari |
—
|
NE NERFINISHED |
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: Padayappa and Neelambari | Statement: [Padayappa, featuresIconicConfrontationBetween, Padayappa and Neelambari]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresIconicConfrontationBetween Context triple: [Padayappa, featuresIconicConfrontationBetween, Padayappa and Neelambari]
-
A.
featuresBattle
Indicates that one entity includes, presents, or involves a battle as a significant element or event.
-
B.
combatBy
Indicates a relationship where one entity engages in combat or fighting through the agency, actions, or involvement of another entity.
-
C.
battleFoughtBy
Indicates that a specific battle was fought by a particular participant or group of participants.
-
D.
hasFightSceneWith
chosen
Indicates that two entities participate together in a fight scene or combat sequence.
-
E.
coveredBattle
Indicates that an entity reported on, documented, or otherwise provided coverage of a particular battle or military engagement.
- 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69ff2d22ffb48190ae58ddf3c7e02869 |
completed | May 9, 2026, 12:48 p.m. |
| PD | Predicate disambiguation | batch_69ff2ac2e1c4819096cc64e94aef2ff0 |
completed | May 9, 2026, 12:38 p.m. |
Created at: April 28, 2026, 12:12 p.m.