Triple
T9644288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xenocongridae |
E233152
|
entity |
| Predicate | hasMember |
P10
|
FINISHED |
| Object | Heteroconger |
E230955
|
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: Heteroconger | Statement: [Xenocongridae, hasMember, Heteroconger]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Heteroconger Context triple: [Xenocongridae, hasMember, Heteroconger]
-
A.
Xenoconger
Xenoconger is a genus of eels within the family Xenocongridae, comprising rare deep-sea conger-like fishes.
-
B.
Oxyconger
Oxyconger is a genus of marine eels known for their elongated bodies and burrowing habits, belonging to the family Muraenesocidae.
-
C.
Xenoconger fryeri
Xenoconger fryeri is a species of marine eel in the family Chlopsidae, known from deep or cryptic reef habitats.
-
D.
Heterocongridae
chosen
Heterocongridae is a family of marine garden eels known for living in colonies with their slender bodies protruding from burrows in sandy or muddy seafloor habitats.
-
E.
Myroconger nigrodentatus
Myroconger nigrodentatus is a rare deep-sea eel species in the genus Myroconger, known from limited specimens collected from the western Pacific Ocean.
- 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_69ca848a5a908190aad251f4137b0c3a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9b7e2c488190b0f0dfa6d82618c8 |
completed | April 1, 2026, 10:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d19f6a7ddc8190b7e8add97b7dc257 |
completed | April 4, 2026, 11:31 p.m. |
Created at: March 30, 2026, 8:12 p.m.