Triple
T30371743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alha-Khand ballads |
E772565
|
entity |
| Predicate | recountsBattleAgainst |
P83829
|
FINISHED |
| Object | Prithviraj Chauhan |
—
|
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: Prithviraj Chauhan | Statement: [Alha-Khand ballads, recountsBattleAgainst, Prithviraj Chauhan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recountsBattleAgainst Context triple: [Alha-Khand ballads, recountsBattleAgainst, Prithviraj Chauhan]
-
A.
battleDescribed
chosen
Indicates that a particular battle is described, depicted, or recounted in the referenced source or representation.
-
B.
sawCombatAgainst
Indicates that one entity directly engaged in combat or battle against another entity.
-
C.
battledIn
Indicates that two or more entities engaged in a battle or conflict that took place at a specific location or during a particular event.
-
D.
coveredBattle
Indicates that an entity reported on, documented, or otherwise provided coverage of a particular battle or military engagement.
-
E.
battleOccurred
Indicates that a conflict or combat event took place between specified parties at a particular time and/or location.
- 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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6828468708190b2fbd5da2de92b22 |
completed | May 2, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:59 p.m.