Triple

T15279780
Position Surface form Disambiguated ID Type / Status
Subject Amur goral E365237 entity
Predicate binomialName P569 FINISHED
Object Naemorhedus caudatus E1148443 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: Naemorhedus caudatus | Statement: [Amur goral, binomialName, Naemorhedus caudatus]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Naemorhedus caudatus
Context triple: [Amur goral, binomialName, Naemorhedus caudatus]
  • A. Naemorhedus chosen
    Naemorhedus is a genus of small, goat-like mountain ungulates known as gorals, native to rugged, forested and rocky regions of Asia.
  • B. 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.
  • C. Ursus arctos crowtheri
    Ursus arctos crowtheri is an extinct subspecies of brown bear that once inhabited North Africa.
  • D. Ratiaria
    Ratiaria was a prominent Roman city and military center on the Danube frontier in the province of Moesia (later Dacia Ripensis), known for its strategic and administrative importance.
  • E. Ursus arctos inopinatus
    Ursus arctos inopinatus is a subspecies of brown bear native to parts of Alaska, characterized by its large size and adaptation to subarctic environments.
  • 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_69d85a103d9081908c1ea6c4c73ac8e3 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e00e504d8c8190ad6c565a31d1a9bd completed April 15, 2026, 10:16 p.m.
NED1 Entity disambiguation (via context triple) batch_69fef895f9708190a44ee7ade1c46a7d completed May 9, 2026, 9:04 a.m.
Created at: April 10, 2026, 3:14 a.m.