Triple
T17273715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Peshawar (1834) |
E419330
|
entity |
| Predicate | commandRoleOf |
P46813
|
FINISHED |
| Object | Hari Singh Nalwa as key Sikh general |
—
|
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: Hari Singh Nalwa as key Sikh general | Statement: [Battle of Peshawar (1834), commandRoleOf, Hari Singh Nalwa as key Sikh general]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandRoleOf Context triple: [Battle of Peshawar (1834), commandRoleOf, Hari Singh Nalwa as key Sikh general]
-
A.
codeRole
Indicates a relationship where an entity serves a specific role or function within a piece of code or software system.
-
B.
roleInCommandStructure
chosen
Indicates that one entity holds a specific position or function within the hierarchical command structure of another entity or organization.
-
C.
possibleRole
Indicates that an entity is capable of or eligible to serve in a particular role or function in a given context.
-
D.
ordinationRole
Indicates the specific religious or ceremonial office, function, or capacity in which an entity is formally ordained.
-
E.
canonicalRole
Indicates that an entity holds a standard, primary, or officially recognized role within a particular context or system.
- 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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42f4c209c81909c713ed78f2cb19a |
completed | April 19, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69e3832c3b98819091967ac7e91ba316 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:40 a.m.