Triple

T156548
Position Surface form Disambiguated ID Type / Status
Subject Prometheus E3193 entity
Predicate mythology P1114 FINISHED
Object Greek 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: Greek mythology | Statement: [Prometheus, mythology, Greek mythology]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mythology
Context triple: [Prometheus, mythology, Greek mythology]
  • A. mythologicalEvent
    Indicates an event or occurrence that takes place within mythological narratives or traditions, often involving gods, heroes, or supernatural phenomena.
  • B. fate
    Indicates that an entity is destined or predetermined to experience a particular outcome or course of events beyond its control.
  • C. roleInTheology
    Indicates the specific function, position, or significance an entity holds within a theological system, doctrine, or belief framework.
  • D. literaryTradition
    Indicates a relationship where a work, practice, or expression belongs to, arises from, or participates in a particular established body of literary customs, styles, or conventions.
  • E. culturalTradition chosen
    Indicates a relationship where certain practices, beliefs, or customs are recognized as part of a shared cultural heritage passed down within a group or society.
  • 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_69a2527757ec819090b8becb2cf1a862 completed Feb. 28, 2026, 2:27 a.m.
NER Named-entity recognition batch_69a258808ff08190a06b6206f635612b completed Feb. 28, 2026, 2:52 a.m.
PD Predicate disambiguation batch_69a2565ded588190a27319aaa0130b4f completed Feb. 28, 2026, 2:43 a.m.
Created at: Feb. 28, 2026, 2:31 a.m.