Triple
T10082602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Malaun |
E213938
|
entity |
| Predicate | helpedDetermine |
P33868
|
FINISHED |
| Object | outcome of the Anglo-Nepalese War |
—
|
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: outcome of the Anglo-Nepalese War | Statement: [Battle of Malaun, helpedDetermine, outcome of the Anglo-Nepalese War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: helpedDetermine Context triple: [Battle of Malaun, helpedDetermine, outcome of the Anglo-Nepalese War]
-
A.
helpedDiscover
Indicates that one entity assisted another entity in the process of discovering or uncovering something.
-
B.
helpedCause
chosen
Indicates that one entity contributed to bringing about, enabling, or facilitating an outcome or event involving another entity.
-
C.
determined
Indicates that an entity has firmly decided on a course of action or conclusion, typically after consideration or effort.
-
D.
helpsIdentify
Indicates a relationship where one entity serves to distinguish, recognize, or determine the identity or characteristics of another entity.
-
E.
decipheredWithHelpOf
Indicates that something was successfully deciphered or interpreted through assistance provided by another entity or resource.
- 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_69ca839bf730819086900c323c9b8c95 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd03482d481908b03d35dc2d16395 |
completed | April 2, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4b97870481908f7a89df10d58a9e |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9 p.m.