Triple
T8699611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kullervo’s Curse |
E206493
|
entity |
| Predicate | depictsCharacterOrigin |
P34184
|
FINISHED |
| Object | Finnish mythology |
—
|
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: Finnish mythology | Statement: [Kullervo’s Curse, depictsCharacterOrigin, Finnish mythology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depictsCharacterOrigin Context triple: [Kullervo’s Curse, depictsCharacterOrigin, Finnish mythology]
-
A.
depictsOriginOf
Indicates that one entity visually represents or illustrates the source, beginning, or point of origin of another entity.
-
B.
characterOrigin
chosen
Indicates the source, background, or initial context from which a character originates.
-
C.
protagonistOrigin
Indicates that one entity is the origin, source, or starting point of the protagonist in a narrative or story.
-
D.
depictsCharacterType
Indicates that one entity visually represents or portrays a character of a specified type or role.
-
E.
depictionBasedOn
Indicates that one depiction is created using another work, image, or representation as its source or reference.
- 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_69ca83555b6c8190abe930dd397e863b |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc58b1434081908f50480bfb6f9d90 |
completed | March 31, 2026, 11:28 p.m. |
| PD | Predicate disambiguation | batch_69cc456bda508190a9aa0fb92760739e |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:34 p.m.