Triple

T16351123
Position Surface form Disambiguated ID Type / Status
Subject Northern Combat Area Command E397062 entity
Predicate aimedToSecure P107402 FINISHED
Object land route from India to China via Burma 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: land route from India to China via Burma | Statement: [Northern Combat Area Command, aimedToSecure, land route from India to China via Burma]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: aimedToSecure
Context triple: [Northern Combat Area Command, aimedToSecure, land route from India to China via Burma]
  • A. securedAgainst
    Indicates that one entity is protected or safeguarded against threats, risks, or harmful actions originating from another entity or source.
  • B. hadGoal chosen
    Indicates that an entity previously possessed or pursued a particular goal or objective.
  • C. aimedToEstablish
    Indicates an intention or effort directed toward creating, founding, or setting up something.
  • D. helpedSecure
    Indicates that one entity contributed to obtaining, protecting, or ensuring the safety or stability of another entity or outcome.
  • E. aimedToLimit
    Indicates an action or policy that was intentionally directed toward restricting, reducing, or constraining something.
  • 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_69d87f26864c819088365ca381a003c2 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e2facb37d0819093fe45446f1e79c1 completed April 18, 2026, 3:30 a.m.
PD Predicate disambiguation batch_69e226f37ecc819082af58b29b4e39d1 completed April 17, 2026, 12:26 p.m.
Created at: April 10, 2026, 5:07 a.m.