Triple

T5049630
Position Surface form Disambiguated ID Type / Status
Subject LernaeanHydra E113751 entity
Predicate hasAlternativeName P39 FINISHED
Object Hydra E481518 NE 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: Hydra | Statement: [LernaeanHydra, hasAlternativeName, Hydra]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hydra
Context triple: [LernaeanHydra, hasAlternativeName, Hydra]
  • A. Hydra
    Hydra is a clandestine, authoritarian terrorist organization in the Marvel universe known for its infiltration of governments and S.H.I.E.L.D. and its recurring clashes with heroes like Captain America.
  • B. Hydra chosen
    Hydra is a many-headed serpent-like monster from Greek mythology, famous for its regenerative heads and its defeat by the hero Heracles.
  • C. Hydra
    Hydra is a widely used network login cracker designed to perform fast, automated brute-force attacks against numerous protocols and services.
  • D. Hydra
    Hydra is a music record label known for releasing works by artists such as The Fireman.
  • E. Hydra
    Hydra is a small, freshwater cnidarian polyp known for its simple tubular body and remarkable ability to regenerate lost or damaged tissues.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69bd44391fc48190a311ce9c826c209b completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd74249a8c8190952680aee06a9286 completed March 20, 2026, 4:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69bea480fee88190a4302301259f29ba completed March 21, 2026, 2 p.m.
Created at: March 20, 2026, 1:37 p.m.