Triple
T582466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Battle of Panipat |
E15086
|
entity |
| Predicate | strengthOfDelhiForces |
P1404
|
FINISHED |
| Object | significantly larger army |
—
|
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: significantly larger army | Statement: [First Battle of Panipat, strengthOfDelhiForces, significantly larger army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strengthOfDelhiForces Context triple: [First Battle of Panipat, strengthOfDelhiForces, significantly larger army]
-
A.
combatantStrength
chosen
Indicates the relative level of power, capability, or effectiveness one combatant has in a conflict or confrontation compared to others.
-
B.
typeOfTroops
Indicates the specific category or kind of military forces involved in or associated with an entity or event.
-
C.
garrisonSize
Indicates the number of troops or defenders stationed at a particular location as its garrison.
-
D.
numberOfTroopsInvolved
Indicates the quantity of military personnel participating in or assigned to a specific operation, event, or engagement.
-
E.
hasDefenderStrength
Indicates that an entity possesses a certain level or measure of defensive capability or protective power.
- 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_69a4935783b8819082b77726ec10cc42 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49b85becc8190b4d98c00e5fa7c04 |
completed | March 1, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69a494c7f9008190bd8d05b4dc2a7c7f |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.