Triple
T589122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lapland War |
E17226
|
entity |
| Predicate | memory |
P15970
|
FINISHED |
| Object | significant event in Finnish Lapland regional history |
—
|
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: significant event in Finnish Lapland regional history | Statement: [Lapland War, memory, significant event in Finnish Lapland regional history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memory Context triple: [Lapland War, memory, significant event in Finnish Lapland regional history]
-
A.
recall
Indicates that an entity retrieves or brings back into awareness information, events, or items that were previously known, experienced, or stored.
-
B.
memoryType
Indicates the specific category or kind of memory associated with an entity or process.
-
C.
memorizedBy
Indicates that some content, information, or material has been learned and retained in memory by a particular entity.
-
D.
memorizationPractice
Indicates engaging in activities or exercises specifically intended to commit information to memory or strengthen recall.
-
E.
save
Indicates preserving or storing something from loss, harm, or use, often for future benefit or protection.
- F. None of above. chosen
Provenance (4 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_69a49379d09c8190ac7e00b24e2810b1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49bb775fc819085b968f8615dca59 |
completed | March 1, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69a494cc13988190892ca10bd7ae9f09 |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a4985ada988190aaea628a9b55bca4 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:33 p.m.