Triple

T34904305
Position Surface form Disambiguated ID Type / Status
Subject Labraunda E1006676 entity
Predicate mainGodAspect P7648 FINISHED
Object Zeus of the Double Axe 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: Zeus of the Double Axe | Statement: [Labraunda, mainGodAspect, Zeus of the Double Axe]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mainGodAspect
Context triple: [Labraunda, mainGodAspect, Zeus of the Double Axe]
  • A. emphasizesAspectOfDeity
    Indicates that one entity highlights, stresses, or draws special attention to a particular attribute, role, or dimension of a deity.
  • B. hasDeityAspect
    Indicates that one entity embodies, represents, or functions as a specific divine aspect or manifestation of another deity.
  • C. mainDeity chosen
    Indicates that one entity serves as the primary or chief deity worshiped, revered, or associated with another entity (such as a religion, temple, or culture).
  • D. mainDeityForm
    Indicates that one entity is the primary or canonical divine form or manifestation of another deity.
  • E. inTheosophyAspect
    Indicates a relationship where one concept, entity, or quality is regarded as an aspect or facet of another within the framework of theosophical doctrine or interpretation.
  • 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_69f76dc1b4a081909b4c6e4d8ec0aa2d completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f78710282c81909146dc0be91e983f completed May 3, 2026, 5:34 p.m.
PD Predicate disambiguation batch_69f784162134819098413482ef52042f completed May 3, 2026, 5:21 p.m.
Created at: May 3, 2026, 4 p.m.