Triple
T37863066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chetak |
E944386
|
entity |
| Predicate | opponentForcesFaced |
P138442
|
FINISHED |
| Object | Mughal Empire |
—
|
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: Mughal Empire | Statement: [Chetak, opponentForcesFaced, Mughal Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opponentForcesFaced Context triple: [Chetak, opponentForcesFaced, Mughal Empire]
-
A.
commandedForcesAgainst
Indicates that one entity held command authority over military or armed forces engaged in opposition to another entity.
-
B.
primaryOpposingForceSize
Indicates the size or magnitude of the main opposing force acting against a subject in a given context.
-
C.
engagedForces
Indicates that one force has actively committed or deployed its military units against another force in combat or operational interaction.
-
D.
auxiliaryTroopsFoughtIn
Indicates that auxiliary troops participated as combatants in a particular battle or military conflict.
-
E.
opposingUnits
chosen
Indicates that two units are in opposition to each other, such as being on rival sides, conflicting forces, or competing entities within a given context.
- 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_69f76eee2f9c8190b1272aa2ee55ebf5 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc995dc2481908b3bd4217f8101e7 |
completed | May 6, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:19 p.m.