Triple

T35415202
Position Surface form Disambiguated ID Type / Status
Subject Zygentoma E1023620 entity
Predicate ancestralFeatures P183370 FINISHED
Object primitively wingless 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: primitively wingless | Statement: [Zygentoma, ancestralFeatures, primitively wingless]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ancestralFeatures
Context triple: [Zygentoma, ancestralFeatures, primitively wingless]
  • A. ancestralStatus
    Indicates that one entity holds a particular ancestral or lineage-based relationship or status in relation to another entity.
  • B. ancestralRange
    Indicates the geographic area or region that a lineage or taxon historically occupied in its evolutionary past.
  • C. ancestralLinks
    Indicates a genealogical relationship where one entity is an ancestor of, or connected through a line of descent to, another entity.
  • D. ancestralDomain
    Indicates that one entity is the traditional or long-held territory or domain from which another entity originates or to which it is ancestrally connected.
  • E. ancestralPlaneAppearance
    Indicates that an entity appears or manifests within an ancestral or spiritual plane in relation to another entity or context.
  • F. None of above. chosen

Provenance (4 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_69f76df54bac8190bd0d3b0eb35cda5f completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f79f7340e4819092a1a47f7028e63f completed May 3, 2026, 7:18 p.m.
PD Predicate disambiguation batch_69f79e4bdbcc8190be7a0d2cf8a77b64 completed May 3, 2026, 7:13 p.m.
PDg Predicate description generation batch_69f79ec14ce08190b22cee0b40d33743 completed May 3, 2026, 7:15 p.m.
Created at: May 3, 2026, 4:03 p.m.