Triple
T31282252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Origo Gentis Langobardorum |
E797702
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | origin legend |
C29101
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: origin legend Context triple: [Origo Gentis Langobardorum, instanceOf, origin legend]
-
A.
legendary narrative
chosen
A legendary narrative is a traditional story, often rooted in historical events or figures, that has been embellished over time with mythical or supernatural elements to convey cultural values or explain the extraordinary.
-
B.
Korean foundation myth
A Korean foundation myth is a traditional narrative that explains the divine or heroic origins of the Korean people, their first rulers, and the establishment of early Korean states.
-
C.
Chinese legend
A Chinese legend is a traditional narrative from Chinese culture that blends historical events, folklore, mythology, and moral lessons, passed down through generations to explain the world and convey cultural values.
-
D.
mountain legend
A mountain legend is a traditional story or myth rooted in a specific mountainous region, often explaining natural features, historical events, or cultural beliefs associated with the landscape.
-
E.
European legend
A European legend is a traditional narrative rooted in the history, folklore, and cultural imagination of European peoples, often blending real events or places with mythical, supernatural, or moral elements.
- F. None of above.
Provenance (1 batch)
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_69f224def9088190a37034eab3daf57f |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:13 p.m.