Triple
T16934074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eleginus gracilis |
E410785
|
entity |
| Predicate | genus |
P87
|
FINISHED |
| Object | Eleginus |
E408221
|
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: Eleginus | Statement: [Eleginus gracilis, genus, Eleginus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eleginus Context triple: [Eleginus gracilis, genus, Eleginus]
-
A.
Sophroniscus
Sophroniscus was an Athenian stonemason and sculptor best known as the father of the philosopher Socrates.
-
B.
Eleginus navaga
chosen
Eleginus navaga is a small Arctic cod species found in the coastal and estuarine waters of the Barents and White Seas, important in local fisheries and adapted to cold, brackish environments.
-
C.
Lychnidus
Lychnidus was an ancient town in the Balkans, near Lake Ohrid, that served as an important stop along the Roman Via Egnatia trade and military route.
-
D.
Hegelochus
Hegelochus was an ancient Greek military figure known for his role in early conflicts of the Greco-Persian Wars.
-
E.
Echemus
Echemus is a figure from Greek mythology known as the Arcadian king who defeated and killed Hyllus, the son of Heracles.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cf2714b08190a2524d5d9578cc87 |
completed | April 18, 2026, 6:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00cfe2d4f48190b965b6c0a3cc0125 |
completed | May 10, 2026, 6:35 p.m. |
Created at: April 10, 2026, 5:30 a.m.