Triple
T25300338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FLN |
E634327
|
entity |
| Predicate | endOfArmedStruggle |
P56137
|
FINISHED |
| Object | 1962 |
—
|
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: 1962 | Statement: [FLN, endOfArmedStruggle, 1962]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfArmedStruggle Context triple: [FLN, endOfArmedStruggle, 1962]
-
A.
announcedEndOfArmedCampaign
Indicates that an entity has formally declared the cessation or termination of its armed or military campaign.
-
B.
endedCeasefire
Indicates that a previously established ceasefire between parties has been terminated or broken.
-
C.
ceasefireEnded
Indicates that a previously established ceasefire between parties has come to an end and hostilities may resume.
-
D.
armedStruggleAgainst
Indicates an organized, often violent resistance or conflict carried out by one party using weapons against another party, typically to oppose or overthrow its control or policies.
-
E.
ceasedArmedCampaign
chosen
Indicates that an entity has stopped or formally ended its use of armed force or military-style violence as a campaign or strategy.
- 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_69e75a972c6481909bc11710e8d30a6c |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48fd66d50819095c3d24c7065c351 |
completed | May 1, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:24 p.m.