Triple

T8632039
Position Surface form Disambiguated ID Type / Status
Subject Sciurini E204424 entity
Predicate notableGenus P12304 FINISHED
Object Tamiasciurus E747080 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: Tamiasciurus | Statement: [Sciurini, notableGenus, Tamiasciurus]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tamiasciurus
Context triple: [Sciurini, notableGenus, Tamiasciurus]
  • A. Tamiasciurus chosen
    Tamiasciurus is a genus of small, vocal North American tree squirrels commonly known as red squirrels, noted for their territorial behavior and conifer seed caching.
  • B. Hyosciurus
    Hyosciurus is a genus of rodents in the squirrel family Sciuridae, comprising distinctive long-nosed squirrels native to Sulawesi, Indonesia.
  • C. Otosciurus
    Otosciurus is a genus of tree squirrels within the tribe Sciurini, comprising species of small to medium-sized rodents typically found in forested habitats.
  • D. Microsciurus
    Microsciurus is a genus of small Neotropical dwarf squirrels found in Central and South American forests.
  • E. Sundasciurus
    Sundasciurus is a genus of Southeast Asian tree squirrels known for their arboreal habits and diversity across forested habitats in the Sunda region.
  • 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_69ca834b903c8190add96cc651e1a477 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc4742a89081909f9f7b3621e50b40 completed March 31, 2026, 10:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69cfab3422008190a42e579a494fa841 completed April 3, 2026, 11:57 a.m.
Created at: March 30, 2026, 6:27 p.m.