Triple

T19744004
Position Surface form Disambiguated ID Type / Status
Subject Bombyx mandarina E474203 entity
Predicate binomialName P569 FINISHED
Object Bombyx mandarina 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: Bombyx mandarina | Statement: [Bombyx mandarina, binomialName, Bombyx mandarina]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bombyx mandarina
Context triple: [Bombyx mandarina, binomialName, Bombyx mandarina]
  • A. Bombyx mandarina chosen
    Bombyx mandarina is a wild silk moth species considered the ancestral progenitor of the domesticated silkworm, Bombyx mori.
  • B. Bombyx horsfieldi
    Bombyx horsfieldi is a species of silkmoth in the genus Bombyx, related to the domesticated silkworm moths.
  • C. Bombyx mori
    Bombyx mori is the domesticated silkworm species widely used in sericulture for producing commercial silk.
  • D. Bombyx incomposita
    Bombyx incomposita is a species of silkmoth in the genus Bombyx, a group best known for the domesticated silk-producing moth Bombyx mori.
  • E. Bombyx shini
    Bombyx shini is a species of silkmoth in the genus Bombyx, related to the domesticated silkworm.
  • 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_69d8e51940a0819087bd2996f98da668 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e652923fd48190982c51c39814fd08 completed April 20, 2026, 4:21 p.m.
Created at: April 10, 2026, 1:47 p.m.