Triple
T25870752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lemminkäinen |
E651747
|
entity |
| Predicate | undertakesQuest |
P41797
|
FINISHED |
| Object | journey to Pohjola |
—
|
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: journey to Pohjola | Statement: [Lemminkäinen, undertakesQuest, journey to Pohjola]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: undertakesQuest Context triple: [Lemminkäinen, undertakesQuest, journey to Pohjola]
-
A.
challengeUndertaken
chosen
Indicates that an entity has accepted and is actively engaging in a specific challenge or demanding task.
-
B.
addsQuest
Indicates that one entity assigns or introduces a quest to another entity or into a system.
-
C.
centralQuest
Indicates that an action, objective, or storyline serves as the primary or main quest within a larger narrative or mission structure.
-
D.
questAssigned
Indicates that a quest has been given by one entity to another, establishing an assignment relationship between them.
-
E.
questType
Indicates the specific category or nature of a quest that characterizes what kind of mission or objective it represents.
- 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_69e7ab3ad9d88190841ddcb93ab02e96 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 22, 2026, 8:11 a.m.