Triple
T23403809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hydra |
E559576
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Hydra (mythological serpent) |
—
|
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: Hydra (mythological serpent) | Statement: [Hydra, namedAfter, Hydra (mythological serpent)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hydra (mythological serpent) Context triple: [Hydra, namedAfter, Hydra (mythological serpent)]
-
A.
Hydra
Hydra is a widely used network login cracker designed to perform fast, automated brute-force attacks against numerous protocols and services.
-
B.
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.
-
C.
Hydra
Hydra is one of Pluto’s small outer moons, discovered in 2005 and named after the many-headed serpent from Greek mythology.
-
D.
Hydra
Hydra is a music record label known for releasing works by artists such as The Fireman.
-
E.
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.
- 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_69e24549610c8190a069d6411ce5f661 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a4e16f9881908ea4bef465e3af11 |
completed | April 29, 2026, 6:27 a.m. |
Created at: April 17, 2026, 5:37 p.m.