Triple
T31742908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNMOGIP |
E810186
|
entity |
| Predicate | ceasefireLineMonitored |
P90746
|
FINISHED |
| Object | Line of Control |
—
|
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: Line of Control | Statement: [UNMOGIP, ceasefireLineMonitored, Line of Control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceasefireLineMonitored Context triple: [UNMOGIP, ceasefireLineMonitored, Line of Control]
-
A.
ceasefireAgreementMonitored
Indicates that the implementation or observance of a ceasefire agreement between parties is being actively supervised, verified, or monitored.
-
B.
ceasefireLine
chosen
Indicates a demarcation line between opposing parties where active hostilities are formally suspended under a ceasefire agreement.
-
C.
ceasefireDeclared
Indicates that a formal agreement has been made to stop hostilities or armed conflict between opposing parties.
-
D.
ceasefireEnded
Indicates that a previously established ceasefire between parties has come to an end and hostilities may resume.
-
E.
ceasefireSupportedBy
Indicates that an entity (such as a person, group, or state) expresses approval of, endorsement for, or backing of a particular ceasefire.
- 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_69f348e233cc819083b6695f70cd75d8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 30, 2026, 11:25 p.m.