Triple

T34868
Position Surface form Disambiguated ID Type / Status
Subject Atlas E693 entity
Predicate causeOfPunishment P694 FINISHED
Object participation in the Titanomachy against the Olympian gods 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: participation in the Titanomachy against the Olympian gods | Statement: [Atlas, causeOfPunishment, participation in the Titanomachy against the Olympian gods]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: causeOfPunishment
Context triple: [Atlas, causeOfPunishment, participation in the Titanomachy against the Olympian gods]
  • A. causeOf chosen
    Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
  • B. penaltyProvision
    Indicates that a rule, contract, or law includes a clause specifying a punishment or sanction for non-compliance or violation.
  • C. reasonForAbolition
    Indicates the cause, justification, or circumstances that led to something being formally ended or abolished.
  • D. causeOfDeath
    Indicates the specific factor, event, or condition that directly resulted in an entity’s death.
  • E. accusationType
    Indicates the specific category or nature of an accusation made by one party against another.
  • 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_69a2479dec388190967ba648663442c9 completed Feb. 28, 2026, 1:40 a.m.
NER Named-entity recognition batch_69a24989c3308190af59dfae37cfc32f completed Feb. 28, 2026, 1:48 a.m.
PD Predicate disambiguation batch_69a24873e97c8190b9e4279e43b6de14 completed Feb. 28, 2026, 1:44 a.m.
Created at: Feb. 28, 2026, 1:44 a.m.