Triple

T16089165
Position Surface form Disambiguated ID Type / Status
Subject Pusa E390314 entity
Predicate notableSpecies P965 FINISHED
Object Pusa caspica E390314 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: Pusa caspica | Statement: [Pusa, notableSpecies, Pusa caspica]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pusa caspica
Context triple: [Pusa, notableSpecies, Pusa caspica]
  • A. Lepus tolai
    Lepus tolai, commonly known as the Tolai hare, is a species of hare native to Central and East Asia, adapted to arid and semi-arid open habitats.
  • B. Pusa chosen
    Pusa is a genus of earless seals that includes several small, cold-water species such as the Caspian seal.
  • C. Pusa
    Pusa is a prominent agricultural research and education hub in Bihar, India, known for hosting major institutions focused on crop science and farming innovation.
  • D. Lepus peguensis
    Lepus peguensis, commonly known as the Burmese hare, is a species of hare native to parts of Southeast Asia, particularly Myanmar and surrounding regions.
  • E. Siberian ibex
    The Siberian ibex is a wild mountain goat native to the rugged ranges of Central Asia, known for its impressive curved horns and adaptation to steep, rocky terrain.
  • 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_69d87f198bc48190a8b7e53ca15b7ead completed April 10, 2026, 4:39 a.m.
NER Named-entity recognition batch_69e1845161908190adca2af94710b2cc completed April 17, 2026, 12:52 a.m.
NED1 Entity disambiguation (via context triple) batch_69fffeed4e008190b1e8d924b9dc9d37 completed May 10, 2026, 3:43 a.m.
Created at: April 10, 2026, 4:59 a.m.