Triple

T1673552
Position Surface form Disambiguated ID Type / Status
Subject Anglo-Nepalese War E36178 entity
Predicate endCondition P29156 FINISHED
Object ratification of the Treaty of Sugauli in 1816 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: ratification of the Treaty of Sugauli in 1816 | Statement: [Anglo-Nepalese War, endCondition, ratification of the Treaty of Sugauli in 1816]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: endCondition
Context triple: [Anglo-Nepalese War, endCondition, ratification of the Treaty of Sugauli in 1816]
  • A. terminationCondition chosen
    Indicates the condition or set of conditions under which an ongoing process, activity, or relationship is brought to an end.
  • B. releaseCondition
    Indicates the circumstances or requirements under which something is allowed to be released or made available.
  • C. triggerCondition
    Indicates the specific circumstances or state under which an associated event, action, or process is initiated or activated.
  • D. hasConditionalEnding
    Indicates that one entity concludes or terminates only if a specified condition involving another entity is met.
  • E. stoppedAt
    Indicates that an entity has come to a halt or pause at a specific location or point in time.
  • 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_69a8861286808190939afff3ce8ee31e completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69ab272a653481908f48aa1eed5de8a4 completed March 6, 2026, 7:12 p.m.
PD Predicate disambiguation batch_69aa61b2f6288190b2348ef7d7e4672d completed March 6, 2026, 5:10 a.m.
Created at: March 4, 2026, 7:29 p.m.