Triple

T206925
Position Surface form Disambiguated ID Type / Status
Subject Hyades E4628 entity
Predicate hasMythologicalConsequence P812 FINISHED
Object transformed into a star cluster 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: transformed into a star cluster | Statement: [Hyades, hasMythologicalConsequence, transformed into a star cluster]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMythologicalConsequence
Context triple: [Hyades, hasMythologicalConsequence, transformed into a star cluster]
  • A. mythologicalEvent
    Indicates an event or occurrence that takes place within mythological narratives or traditions, often involving gods, heroes, or supernatural phenomena.
  • B. hasConsequence chosen
    Indicates that one event, action, or condition leads to or results in another as its outcome or effect.
  • C. hasMythSource
    Indicates that something derives from, is based on, or is supported by a particular myth or mythological source.
  • D. hasCosmogony
    Indicates that an entity is associated with, or characterized by, a particular account or doctrine of the origin and development of the universe or cosmos.
  • E. hasDeity
    Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
  • 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_69a25737567c81908f9c505300239181 completed Feb. 28, 2026, 2:47 a.m.
NER Named-entity recognition batch_69a25e2aba74819093eddd8d820260c0 completed Feb. 28, 2026, 3:16 a.m.
PD Predicate disambiguation batch_69a25b4c7f908190876c1041db52dffc completed Feb. 28, 2026, 3:04 a.m.
Created at: Feb. 28, 2026, 2:51 a.m.