Triple
T37970466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Amritsar |
E947268
|
entity |
| Predicate | sideLedBy |
P156596
|
FINISHED |
| Object | Sikh forces |
—
|
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: Sikh forces | Statement: [Battle of Amritsar, sideLedBy, Sikh forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sideLedBy Context triple: [Battle of Amritsar, sideLedBy, Sikh forces]
-
A.
side2Leader
chosen
Indicates that the referenced entity serves as the leader or primary representative of the second side in a two-sided relationship, interaction, or conflict.
-
B.
leaderFrom
Indicates that an entity serves or has served as a leader originating from, representing, or associated with a specified place or organization.
-
C.
supportedLeader
Indicates that one entity actively backed, endorsed, or provided assistance to a particular leader.
-
D.
leader2
Indicates that one entity serves as a leader, chief, or primary authority figure in relation to another entity.
-
E.
wirdGeleitetVon
Indicates that something (such as an organization, project, or process) is being led or directed by a specific person or entity.
- 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_69f76ef7db908190bba6086673a32300 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.