Triple
T29186189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kilinochchi |
E739874
|
entity |
| Predicate | postWarChallenge |
P12962
|
FINISHED |
| Object | landmine clearance |
—
|
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: landmine clearance | Statement: [Kilinochchi, postWarChallenge, landmine clearance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postWarChallenge Context triple: [Kilinochchi, postWarChallenge, landmine clearance]
-
A.
postWarFunction
Indicates how something operated, was used, or what role it served in the period following a war.
-
B.
postWarOrder
Indicates the arrangement of political, economic, and social relations established among actors after a war has ended.
-
C.
postwarOutcome
chosen
Indicates the result or consequences that follow for a party or situation after a war has ended.
-
D.
postWarHistory
Indicates a relationship where something concerns, describes, or belongs to the historical period and events following a specific war.
-
E.
postwarActivity
Indicates activities, roles, or developments associated with an entity specifically in the period following a war or major conflict.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6638722fc819098f18314dfa88a6c |
completed | May 2, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, noon