Triple

T29572173
Position Surface form Disambiguated ID Type / Status
Subject Silvian dynasty E753341 entity
Predicate hasMythicSuccessor P171277 FINISHED
Object Roman Kingdom NE NERFINISHED

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 Kingdom | Statement: [Silvian dynasty, hasMythicSuccessor, Roman Kingdom]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMythicSuccessor
Context triple: [Silvian dynasty, hasMythicSuccessor, Roman Kingdom]
  • A. hasMythicMotif
    Indicates that one entity features, embodies, or is associated with a particular mythic motif found in the other entity.
  • B. isMythicPrototypeOf
    Indicates that one entity serves as the mythic or legendary archetype, model, or original form upon which the other entity is based or derived.
  • C. hasMythicTheme
    Indicates that something embodies, references, or is characterized by a mythic or mythological theme.
  • D. hasMythicOrderOfFormation
    Indicates that there exists a specific mythic or legendary sequence in which the related entities are believed to have been formed or brought into existence.
  • E. hasMythicFounder
    Indicates that an entity is traditionally believed to have been founded or established by a legendary or mythological figure rather than a historically verified person.
  • F. None of above. chosen

Provenance (4 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_69f0ef7fcb4881908a933110adb9bda1 completed April 28, 2026, 5:33 p.m.
NER Named-entity recognition batch_69f69f80b62c8190bf2af2be0d3a7df8 completed May 3, 2026, 1:06 a.m.
PD Predicate disambiguation batch_69f69d1a37e081908d1d86b90ff502bd completed May 3, 2026, 12:55 a.m.
PDg Predicate description generation batch_69f69dfbf6ac8190ba2e6fc0adfd8b73 completed May 3, 2026, 12:59 a.m.
Created at: April 28, 2026, 5:59 p.m.