Triple
T19730011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Messier 83 |
E473825
|
entity |
| Predicate | locatedInConstellation |
P40
|
FINISHED |
| Object | 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: Hydra | Statement: [Messier 83, locatedInConstellation, Hydra]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hydra Context triple: [Messier 83, locatedInConstellation, Hydra]
-
A.
Hydra
Hydra is a many-headed serpent-like monster from Greek mythology, famous for its regenerative heads and its defeat by the hero Heracles.
-
B.
Hydra
Hydra is one of Pluto’s small outer moons, discovered in 2005 and named after the many-headed serpent from Greek mythology.
-
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
chosen
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 (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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e649fbeaf081909e9356229eaf84dd |
completed | April 20, 2026, 3:45 p.m. |
Created at: April 10, 2026, 1:47 p.m.