Triple

T1741940
Position Surface form Disambiguated ID Type / Status
Subject Hydropotes inermis lacks antlers E38252 entity
Predicate isNotedAs P22 FINISHED
Object distinctive feature of Hydropotes inermis LITERAL 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: distinctive feature of Hydropotes inermis | Statement: [Hydropotes inermis lacks antlers, isNotedAs, distinctive feature of Hydropotes inermis]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isNotedAs
Context triple: [Hydropotes inermis lacks antlers, isNotedAs, distinctive feature of Hydropotes inermis]
  • A. isNotedOn
    Indicates that information about one entity is recorded, mentioned, or annotated on another entity (such as a document, record, or medium).
  • B. notedIn
    Indicates that information about one entity is mentioned, recorded, or referenced within another entity, such as a document, record, or source.
  • C. notableState
    Indicates that an entity is significantly associated with, recognized in, or prominently linked to a particular state (such as a U.S. state or similar regional jurisdiction).
  • D. notableFor chosen
    Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
  • E. notablePass
    Indicates that one entity is recognized for having successfully passed or cleared another entity, such as a test, threshold, or evaluation, in a notably significant way.
  • F. None of above.

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_69a8862b01a48190ab47209063af82d9 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69ab3c2559ac8190905186406fcaccb9 completed March 6, 2026, 8:42 p.m.
PD Predicate disambiguation batch_69aa61c4023c819099cbe439aefda71f completed March 6, 2026, 5:10 a.m.
Created at: March 4, 2026, 7:30 p.m.