Triple
T5564692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FLNC |
E145852
|
entity |
| Predicate | announcedEndOfArmedStruggle |
P20155
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [FLNC, announcedEndOfArmedStruggle, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: announcedEndOfArmedStruggle Context triple: [FLNC, announcedEndOfArmedStruggle, 2014]
-
A.
announcedEndOfArmedCampaign
chosen
Indicates that an entity has formally declared the cessation or termination of its armed or military campaign.
-
B.
liberationAchievedBy
Indicates that a state of liberation or freedom is brought about or attained through a specific action, process, or agent.
-
C.
announcedCeasefire
Indicates that an entity has formally declared the suspension of hostilities or fighting, typically within a conflict or war.
-
D.
liberationDate
Indicates the date on which an entity was freed, released, or liberated from a prior state of control, confinement, or oppression.
-
E.
ceasefireEnded
Indicates that a previously established ceasefire between parties has come to an end and hostilities may resume.
- 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_69c008fdae24819081aa002ad99cd966 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c02033cc308190895f13454c57f452 |
completed | March 22, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69c01b12826c8190969a584d0f53aa44 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:36 p.m.