Triple

T30862684
Position Surface form Disambiguated ID Type / Status
Subject Petaurista yunanensis E786103 entity
Predicate patagiumExtendsBetween P46702 FINISHED
Object forelimbs and hindlimbs 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: forelimbs and hindlimbs | Statement: [Petaurista yunanensis, patagiumExtendsBetween, forelimbs and hindlimbs]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: patagiumExtendsBetween
Context triple: [Petaurista yunanensis, patagiumExtendsBetween, forelimbs and hindlimbs]
  • A. extendsBetween chosen
    Indicates a relationship where one entity spans or stretches from one point, object, or boundary to another, covering the space between them.
  • B. mayExtendTo
    Indicates that something has the potential or permission to reach, continue, or be applied up to a specified limit, scope, or boundary.
  • C. extendsTo
    Indicates that one entity reaches, stretches, or continues its scope, influence, or coverage up to or into another entity.
  • D. gapBetween
    Indicates the spatial or temporal distance or separation that exists between two entities.
  • E. metBetween
    Indicates that two or more entities had an in-person or virtual meeting or encounter with each other during a specified time or context.
  • 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_69f224b91c14819084e764832fe67a57 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f691aa2ad48190b80eff3be46cdf1e completed May 3, 2026, 12:07 a.m.
PD Predicate disambiguation batch_69f68b7d2794819092fef8a63f4f3de8 completed May 2, 2026, 11:40 p.m.
Created at: April 29, 2026, 8:47 p.m.