Triple
T15626384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johnson Line and Macartney–MacDonald Line proposals |
E375689
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | India–China border proposal |
C5772
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: India–China border proposal Context triple: [Johnson Line and Macartney–MacDonald Line proposals, instanceOf, India–China border proposal]
-
A.
India–Russia military cooperation activity
India–Russia military cooperation activity encompasses the joint defense initiatives, arms trade, technology transfers, training exercises, and strategic collaborations undertaken between India and Russia to enhance their mutual security and military capabilities.
-
B.
border conflict
A border conflict is a dispute between neighboring states or groups over the ownership, control, or demarcation of a shared territorial boundary.
-
C.
border treaty
A border treaty is a formal agreement between two or more states that defines, clarifies, or adjusts their mutual territorial boundaries and the rules governing them.
-
D.
India–France military cooperation activity
India–France military cooperation activity encompasses joint defense initiatives, including strategic dialogues, combined exercises, technology collaboration, and arms trade aimed at enhancing bilateral security and interoperability between the Indian and French armed forces.
-
E.
disputed territory
chosen
A disputed territory is a geographic area over which two or more parties claim sovereignty or control, without mutual agreement on its legal or political status.
- F. None of above.
Provenance (1 batch)
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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 4:14 a.m.