Triple

T9799998
Position Surface form Disambiguated ID Type / Status
Subject Leporidae E237811 entity
Predicate includesGenus P1393 FINISHED
Object Lepus E237810 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: Lepus | Statement: [Leporidae, includesGenus, Lepus]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lepus
Context triple: [Leporidae, includesGenus, Lepus]
  • A. Lepus chosen
    Lepus is a genus of fast-running mammals commonly known as hares and jackrabbits, found across much of the world in open and semi-open habitats.
  • B. Lepus
    Lepus is a small southern constellation located just below Orion, traditionally representing a hare.
  • C. Lapine
    Lapine is a surname most notably associated with American theater director and playwright James Lapine, known for his collaborations with composer Stephen Sondheim.
  • D. Lepus victoriae
    Lepus victoriae, commonly known as the African savanna hare, is a species of hare native to sub-Saharan Africa, typically inhabiting open grasslands and savannas.
  • E. 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.
  • 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_69ca84dd4608819097ff4ed00feca280 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cda628fe0081909d2fbac3bd56ee84 completed April 1, 2026, 11:11 p.m.
NED1 Entity disambiguation (via context triple) batch_69d3170e01408190969fdd8c366f9276 completed April 6, 2026, 2:14 a.m.
Created at: March 30, 2026, 8:29 p.m.