Triple

T23067873
Position Surface form Disambiguated ID Type / Status
Subject Stheno E575101 entity
Predicate mortalityComparedToMedusa P54687 FINISHED
Object immortalWhileMedusaIsMortal 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: immortalWhileMedusaIsMortal | Statement: [Stheno, mortalityComparedToMedusa, immortalWhileMedusaIsMortal]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mortalityComparedToMedusa
Context triple: [Stheno, mortalityComparedToMedusa, immortalWhileMedusaIsMortal]
  • A. mortalityRate
    Indicates the proportion of individuals in a defined population that die within a specified time period.
  • B. medusaFunction
    Indicates a functional or operational relationship analogous to the mythological Medusa, where one entity exerts a transformative, paralyzing, or immobilizing effect on another.
  • C. mortalStatus chosen
    Indicates the state or condition of an entity with respect to being mortal, immortal, or otherwise subject to death.
  • D. associatedWithMortal
    Indicates a relationship where an entity is connected or linked in some way to a mortal being (a being subject to death).
  • E. hasDeathGod
    Indicates that an entity is associated with, served by, or under the dominion of a specific deity or supernatural being of death.
  • 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_69e245bd6e4c8190bb8942245b68cad5 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f189a5aa4081909b3f0dc92877323d completed April 29, 2026, 4:31 a.m.
PD Predicate disambiguation batch_69ef89d5f71881908b9f9d0c8aab278c completed April 27, 2026, 4:07 p.m.
Created at: April 17, 2026, 3:55 p.m.