Triple

T10067330
Position Surface form Disambiguated ID Type / Status
Subject Lathyrus E213133 entity
Predicate hasSpecies P965 FINISHED
Object Lathyrus cicera E213133 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: Lathyrus cicera | Statement: [Lathyrus, hasSpecies, Lathyrus cicera]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lathyrus cicera
Context triple: [Lathyrus, hasSpecies, Lathyrus cicera]
  • A. Lathyrus chosen
    Lathyrus is a genus of flowering plants in the legume family, best known for species like the ornamental sweet pea.
  • B. Pisum
    Pisum is a small genus of flowering legume plants best known for the garden pea, a key model organism in genetics and an important food crop.
  • C. Vetch
    Vetch is a surname most notably associated with Samuel Vetch, a colonial governor of Nova Scotia in the early 18th century.
  • D. Onobrychis
    Onobrychis is a genus of flowering legumes commonly known as sainfoins, valued as forage plants in temperate regions.
  • E. Lupinus angustifolius
    Lupinus angustifolius is a species of narrow-leaved lupin widely cultivated as a grain legume for its high-protein seeds and use in animal feed and soil improvement.
  • 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_69ca83977128819084084eb7d1d8c52a completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cdcff63a4c8190bb08a0428aafa189 completed April 2, 2026, 2:09 a.m.
NED1 Entity disambiguation (via context triple) batch_69d354d7202c81908d42107c346900dc completed April 6, 2026, 6:38 a.m.
Created at: March 30, 2026, 8:58 p.m.