Triple
T34161918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bölverk |
E876299
|
entity |
| Predicate | timeOfMythRecording |
P93018
|
FINISHED |
| Object | 13th century |
—
|
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: 13th century | Statement: [Bölverk, timeOfMythRecording, 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfMythRecording Context triple: [Bölverk, timeOfMythRecording, 13th century]
-
A.
timeInMyth
Indicates that an entity exists or occurs during a specific time period within a mythological narrative or tradition.
-
B.
chronologyWithinMythos
Indicates that one event, story, or element occurs at a specific position or order within the internal timeline of a particular mythos or fictional universe.
-
C.
timeRecorded
chosen
Indicates that a specific point or period in time has been captured and stored as associated with an event, action, or state.
-
D.
timeDivisionMyth
Indicates a mythological or narrative relationship in which a story explains how time is divided into distinct units or periods.
-
E.
mythologicalStartDateInGregorian
Indicates the date, expressed in the Gregorian calendar, on which a mythological event, era, or figure is considered to have begun.
- 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_69f349ac987481908a8e6053f665bc8b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
Created at: May 1, 2026, 1:54 a.m.