Triple

T24119309
Position Surface form Disambiguated ID Type / Status
Subject Microchiroptera E597606 entity
Predicate historicallyDividedOrder P20121 FINISHED
Object Chiroptera NE NERFINISHED

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: Chiroptera | Statement: [Microchiroptera, historicallyDividedOrder, Chiroptera]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicallyDividedOrder
Context triple: [Microchiroptera, historicallyDividedOrder, Chiroptera]
  • A. historicallyDividedInto chosen
    Indicates that an entity was separated into multiple distinct parts or regions during a past historical period.
  • B. hasHistoricalDivision
    Indicates that an entity has undergone a formal separation or split into distinct parts at some point in its history.
  • C. traditionallyDividedInto
    Indicates that something is customarily or historically separated into specific parts, sections, or categories according to established tradition.
  • D. historicalAlignmentOf
    Indicates a relationship where entities share or are compared based on their positions, roles, or associations within a specific historical context or period.
  • E. dividedIn
    Indicates that one entity is partitioned or separated into multiple distinct parts, sections, or groups represented by another entity.
  • 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_69e288c74200819098ab875b592cb39f completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f1dee1a2608190870ade02495c5ebe completed April 29, 2026, 10:35 a.m.
PD Predicate disambiguation batch_69f1765650fc8190a6bc1eb512b240bf completed April 29, 2026, 3:09 a.m.
Created at: April 17, 2026, 11:05 p.m.