Triple
T28431496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglo-Nepalese War |
E715142
|
entity |
| Predicate | endTreaty |
P121621
|
FINISHED |
| Object | Treaty of Sugauli |
—
|
NE NERFINISHED |
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: Treaty of Sugauli | Statement: [Anglo-Nepalese War, endTreaty, Treaty of Sugauli]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endTreaty Context triple: [Anglo-Nepalese War, endTreaty, Treaty of Sugauli]
-
A.
treatyEnded
Indicates that a formal treaty or agreement between parties has come to an end or has been terminated.
-
B.
treatyEndedConflict
chosen
Indicates that a formal treaty brought an existing conflict between parties to an official end.
-
C.
treatyConcluded
Indicates that a formal agreement or treaty has been officially finalized and brought into force between the involved parties.
-
D.
treatyRelatedToDissolution
Indicates that a treaty is connected to, concerns, or results in the dissolution or termination of a political, legal, or organizational entity.
-
E.
treatyAfter
Indicates that a treaty or formal agreement was established after a specified prior event, condition, or relationship between the entities.
- 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_69efd6b253888190b3c7222ed6a403a8 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f64e37f7fc819083809149b6661e3c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 1:40 a.m.