Triple
T19256042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hydra |
E481518
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | Lernaean Hydra |
—
|
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: Lernaean Hydra | Statement: [Hydra, alsoKnownAs, Lernaean Hydra]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lernaean Hydra Context triple: [Hydra, alsoKnownAs, Lernaean Hydra]
-
A.
LernaeanHydra
chosen
The Lernaean Hydra is a many-headed serpent-like monster from Greek mythology, famed for its regenerative heads and its defeat as one of Heracles’ Twelve Labors.
-
B.
Hydra
Hydra is a music record label known for releasing works by artists such as The Fireman.
-
C.
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.
-
D.
Hydra
Hydra is a widely used network login cracker designed to perform fast, automated brute-force attacks against numerous protocols and services.
-
E.
Hydra
Hydra is a many-headed serpent-like monster from Greek mythology, famous for its regenerative heads and its defeat by the hero Heracles.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb3572c08190a55f1c71cdb18b42 |
completed | April 20, 2026, 10:08 a.m. |
Created at: April 10, 2026, 1:28 p.m.