Triple
T19230128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slavs and Vikings Festival |
E480846
|
entity |
| Predicate | timePeriodReenacted |
P59344
|
FINISHED |
| Object | early Middle Ages |
—
|
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: early Middle Ages | Statement: [Slavs and Vikings Festival, timePeriodReenacted, early Middle Ages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodReenacted Context triple: [Slavs and Vikings Festival, timePeriodReenacted, early Middle Ages]
-
A.
timePeriodRecreated
chosen
Indicates that an entity has been recreated, represented, or simulated to reflect the characteristics of a specific historical or temporal period.
-
B.
hasReenactments
Indicates that an event, scene, or situation is represented again through staged or dramatized performances.
-
C.
timePeriodReflected
Indicates that one entity represents or corresponds to the time period associated with another entity.
-
D.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
E.
timePeriodFormulated
Indicates the time period during which something (such as a concept, theory, or plan) was formulated or developed.
- 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_69d8e8ccb8f48190ad420098e74fb1db |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fa9be0d08190afe6040e0cf9c737 |
completed | April 20, 2026, 10:06 a.m. |
| PD | Predicate disambiguation | batch_69e4dcfae6f081909cc173cf71a5005c |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:25 p.m.