Triple

T10314783
Position Surface form Disambiguated ID Type / Status
Subject Sebastidae E241987 entity
Predicate notableGenus P12304 FINISHED
Object Sebastolobus E855011 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: Sebastolobus | Statement: [Sebastidae, notableGenus, Sebastolobus]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sebastolobus
Context triple: [Sebastidae, notableGenus, Sebastolobus]
  • A. Sebastolobus chosen
    Sebastolobus is a genus of deep-sea rockfish known for their spiny bodies and adaptation to life on the ocean floor.
  • B. Hemibarbus
    Hemibarbus is a genus of freshwater cypriniform fishes native to East Asia, commonly found in rivers and streams.
  • C. Gobiobotia
    Gobiobotia is a genus of small freshwater cyprinid fishes native to East Asia, typically inhabiting rivers and streams.
  • D. Muraenesox
    Muraenesox is a genus of large marine eels commonly known as pike congers, found in tropical and subtropical coastal waters.
  • E. Esomus
    Esomus is a genus of small Asian freshwater cyprinid fishes commonly known as flying barbs, noted for their elongated bodies and barbels.
  • 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_69d381ac38808190a8ca7457c85b625b completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4d35b7c688190b68613f28b5511bc completed April 7, 2026, 9:50 a.m.
NED1 Entity disambiguation (via context triple) batch_69d75036ed008190aee48695ad7f857d completed April 9, 2026, 7:07 a.m.
Created at: April 6, 2026, 11:48 a.m.