Triple
T26131527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runo XXXI |
E659260
|
entity |
| Predicate | workIncludedWith |
P10663
|
FINISHED |
| Object | other runos of the Kalevala compiled by Elias Lönnrot |
—
|
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: other runos of the Kalevala compiled by Elias Lönnrot | Statement: [Runo XXXI, workIncludedWith, other runos of the Kalevala compiled by Elias Lönnrot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workIncludedWith Context triple: [Runo XXXI, workIncludedWith, other runos of the Kalevala compiled by Elias Lönnrot]
-
A.
workIncludes
chosen
Indicates that a work (such as a project, document, or creative piece) contains or incorporates another specified component, part, or element.
-
B.
includedWorkOn
Indicates that one entity contains, features, or incorporates another entity as a work or component within it.
-
C.
workWith
Indicates that one entity collaborates or engages in work-related activities together with another entity.
-
D.
worksTo
Indicates that one entity performs work or exerts effort in order to achieve, support, or contribute to another entity or outcome.
-
E.
worksFrom
Indicates that an entity performs its work or duties starting from or based at a specified location or source.
- 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60b931a7c819088d55031d502a9e0 |
completed | May 2, 2026, 2:34 p.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 8:15 p.m.