Triple

T22377802
Position Surface form Disambiguated ID Type / Status
Subject Esquiline Venus E553192 entity
Predicate subjectHasMythology P9595 FINISHED
Object Roman mythology 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: Roman mythology | Statement: [Esquiline Venus, subjectHasMythology, Roman mythology]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: subjectHasMythology
Context triple: [Esquiline Venus, subjectHasMythology, Roman mythology]
  • A. mythologicalContent
    Indicates that the subject contains, references, or is associated with myths, mythological narratives, or myth-based elements.
  • B. mythologicalCategory
    Indicates that one entity is classified as belonging to the mythological type, group, or category represented by the other entity.
  • C. linkedToMythology chosen
    Indicates that something has a connection or association with a mythological tradition, figure, story, or theme.
  • D. hasMythologicalBasis
    Indicates that something is founded on, derived from, or significantly influenced by a mythological story, figure, or tradition.
  • E. hasMythologicalDomain
    Indicates that a mythological figure, deity, or entity is associated with or rules over a particular conceptual or physical domain (such as the sea, war, or the underworld).
  • 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_69e11e4c03248190a26a5060ea6973ee completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f158292d80819094f474c0e9e14caf completed April 29, 2026, 1 a.m.
PD Predicate disambiguation batch_69e73011e6388190a05edf137f488441 completed April 21, 2026, 8:06 a.m.
Created at: April 16, 2026, 8:45 p.m.