Triple
T23151798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kashmir front |
E578340
|
entity |
| Predicate | ceasefireEffectiveOn |
P23514
|
FINISHED |
| Object | 1 January 1949 |
—
|
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: 1 January 1949 | Statement: [Kashmir front, ceasefireEffectiveOn, 1 January 1949]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceasefireEffectiveOn Context triple: [Kashmir front, ceasefireEffectiveOn, 1 January 1949]
-
A.
ceasefireDate
chosen
Indicates the date on which a ceasefire between parties is formally initiated, agreed, or comes into effect.
-
B.
ceasefireEnded
Indicates that a previously established ceasefire between parties has come to an end and hostilities may resume.
-
C.
ceasefireDuration
Indicates the length of time for which a ceasefire agreement between parties is intended to remain in effect.
-
D.
ceasefireDeclared
Indicates that a formal agreement has been made to stop hostilities or armed conflict between opposing parties.
-
E.
ceasefireWith
Indicates a mutual agreement between parties to stop hostilities or armed conflict, typically for a specified period or under certain conditions.
- 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_69e245fb8de081908f0eba7b5fd75bc4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18ef982488190984a6358bdcd577c |
completed | April 29, 2026, 4:54 a.m. |
| PD | Predicate disambiguation | batch_69ef89f83b108190aaaa1db6221fc163 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:01 p.m.