Triple
T14801232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khanwa |
E347914
|
entity |
| Predicate | battleWeaponry |
P7745
|
FINISHED |
| Object | use of gunpowder artillery by Mughals |
—
|
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: use of gunpowder artillery by Mughals | Statement: [Khanwa, battleWeaponry, use of gunpowder artillery by Mughals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleWeaponry Context triple: [Khanwa, battleWeaponry, use of gunpowder artillery by Mughals]
-
A.
weapon
Indicates that one entity is used as a weapon by, or serves as the weapon of, another entity.
-
B.
weaponsUsed
Indicates that one entity employed or utilized another entity as a weapon in carrying out an action or event.
-
C.
weaponsBay
Indicates that one entity serves as the weapons bay (storage or housing area for weapons) of another entity.
-
D.
armamentCategory
Indicates the classification of a weapon or military equipment according to its type or role in armament systems.
-
E.
typicalWeapon
chosen
Indicates that the object is a weapon commonly or characteristically used by the subject.
- 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_69d822ea8b7c819097dfadf3d45545e6 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decd62c36c81909c2993dc7d1a79ea |
completed | April 14, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69de8c0ef8a4819092d84478b1f56db1 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:31 a.m.