Triple

T11380358
Position Surface form Disambiguated ID Type / Status
Subject Archosauria E269576 entity
Predicate divergedFromLepidosauromorpha P63017 FINISHED
Object in the Permian or early Triassic 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: in the Permian or early Triassic | Statement: [Archosauria, divergedFromLepidosauromorpha, in the Permian or early Triassic]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: divergedFromLepidosauromorpha
Context triple: [Archosauria, divergedFromLepidosauromorpha, in the Permian or early Triassic]
  • A. divergenceTime chosen
    Indicates the point in time at which two entities, lineages, or states split from a common origin or began to differ from each other.
  • B. differsFromMetatheriansBy
    Indicates that one entity is characterized by traits or features that are different from those of metatherians.
  • C. evolvedWith
    Indicates that two or more entities have undergone evolutionary change in mutual influence or parallel over time.
  • D. formerSpecies
    Indicates that an entity was previously classified as a particular species but no longer holds that species status.
  • E. vertebrate
    Indicates that the subject is an animal possessing a backbone or spinal column.
  • 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_69d6aacca1048190b39dbbc2174616fa completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d800160a1c81909d115bf89fe54a49 completed April 9, 2026, 7:37 p.m.
PD Predicate disambiguation batch_69d7e7022d508190996f9be0847c2b41 completed April 9, 2026, 5:50 p.m.
Created at: April 8, 2026, 9:34 p.m.