Triple
T30016764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | India–Bhutan relations |
E762616
|
entity |
| Predicate | securityCooperationIncludes |
P37951
|
FINISHED |
| Object | border management |
—
|
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: border management | Statement: [India–Bhutan relations, securityCooperationIncludes, border management]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityCooperationIncludes Context triple: [India–Bhutan relations, securityCooperationIncludes, border management]
-
A.
securityCooperationFormat
Indicates the type or structure of collaborative security arrangements or mechanisms established between entities.
-
B.
securityCooperatesWith
Indicates that one security-related entity collaborates or works jointly with another on security matters or activities.
-
C.
securityCollaboration
chosen
Indicates a cooperative relationship in which entities work together to plan, implement, or maintain security measures, policies, or defenses.
-
D.
securityDependence
Indicates a relationship where one entity relies on another to ensure its safety, protection, or defense from threats.
-
E.
securityArrangementsBy
Indicates that one entity is responsible for providing, organizing, or overseeing security arrangements for another entity or situation.
- 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_69f2246b0c84819094f1250b6a02d277 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 29, 2026, 6:46 p.m.