Triple
T17190094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Labyrinth of Porsenna (legendary) |
E417206
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Etruscan legend |
C12784
|
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: Etruscan legend Context triple: [Labyrinth of Porsenna (legendary), instanceOf, Etruscan legend]
-
A.
Etruscan god
An Etruscan god is a divine being from the ancient Etruscan religion, associated with specific aspects of nature, fate, or human activity and often later syncretized with Greek and Roman deities.
-
B.
Roman legendary characters
Roman legendary characters are mythic or semi-mythic figures from Rome’s foundational and heroic traditions whose stories blend history, folklore, and moral exempla to express Roman values and identity.
-
C.
European legend
chosen
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.
-
D.
Etruscan inscription
An Etruscan inscription is a text written in the ancient Etruscan language, typically carved or painted on durable materials such as stone, metal, or pottery, providing evidence of the culture, religion, and daily life of the Etruscan civilization.
-
E.
Etruscan city
An Etruscan city is an urban center of the ancient Etruscan civilization in central Italy, characterized by fortified hilltop locations, planned street layouts, religious and civic monuments, and a strong regional trade and cultural network.
- 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_69d886d6ba8c819093215917b3d01689 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:37 a.m.