Triple
T23000000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corvus |
E572608
|
entity |
| Predicate | borderedBy |
P224
|
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: [Corvus, borderedBy, Hydra]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hydra Context triple: [Corvus, borderedBy, 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
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
chosen
Hydra is the largest and longest of the 88 modern constellations, representing a water serpent in the southern sky.
-
D.
Hydra
Hydra is a U.S. dollar–pegged stablecoin designed to maintain a stable value relative to the USD.
-
E.
Hydra
Hydra is a widely used network login cracker designed to perform fast, automated brute-force attacks against numerous protocols and services.
- 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_69e245b6a3ac81908087599eefe3e365 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f182f6484c8190bfe3f7ea894c43d8 |
completed | April 29, 2026, 4:03 a.m. |
Created at: April 17, 2026, 3:50 p.m.