Triple
T11885784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Chamkaur |
E282776
|
entity |
| Predicate | strengthSikhSide |
P102065
|
FINISHED |
| Object | small band of Sikhs |
—
|
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: small band of Sikhs | Statement: [Battle of Chamkaur, strengthSikhSide, small band of Sikhs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strengthSikhSide Context triple: [Battle of Chamkaur, strengthSikhSide, small band of Sikhs]
-
A.
side2Strength
Indicates the magnitude or level of strength associated with the second side in a relationship, comparison, or interaction.
-
B.
strength_Maratha_side
Indicates the level or extent of military or combat power associated with the Maratha side in a conflict or comparison.
-
C.
strength_British_side
Indicates the level or measure of military or strategic power possessed by the British side in a given context.
-
D.
forcesSide2
Indicates that one entity compels or coerces another entity to take or remain on a particular side or position in a situation or conflict.
-
E.
totalStrength
Indicates the overall magnitude or combined level of strength associated with an entity or group of entities.
- F. None of above. chosen
Provenance (4 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8d3a13370819086386fecb99e4f0b |
completed | April 10, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69d8bb272f88819090c37c944c5a60ab |
completed | April 10, 2026, 8:56 a.m. |
| PDg | Predicate description generation | batch_69d8d399d58c81908dab572aa82426d7 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 8, 2026, 9:44 p.m.