Triple

T38560207
Position Surface form Disambiguated ID Type / Status
Subject Mordarski E928057 entity
Predicate worksOnTaxonRank P68502 FINISHED
Object order 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: order | Statement: [Mordarski, worksOnTaxonRank, order]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: worksOnTaxonRank
Context triple: [Mordarski, worksOnTaxonRank, order]
  • A. worksOnTaxa
    Indicates that an agent is engaged in research, study, or other work involving specific taxa or taxonomic groups.
  • B. studiedTaxonRank
    Indicates that an entity’s study or research activity is specifically focused on organisms at a particular taxonomic rank (e.g., species, genus, family).
  • C. hasWorkedOnTaxonRank chosen
    Indicates that an entity (typically a person or agent) has conducted work, research, or activities specifically related to a taxonomic rank (such as species, genus, family, etc.).
  • D. taxonRank
    Indicates the formal hierarchical rank (such as species, genus, family, etc.) that a given taxon occupies within a biological classification system.
  • E. establishedTaxonomicRank
    Indicates that one entity has formally defined or assigned the taxonomic rank or classification level of another entity within a biological taxonomy.
  • 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_69f76eb8d1808190a588af29d8b266d6 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fd389cb28c819099a77e28d25f258a completed May 8, 2026, 1:13 a.m.
PD Predicate disambiguation batch_69fd3826d8048190ada79a5868d1d7f3 completed May 8, 2026, 1:11 a.m.
Created at: May 3, 2026, 4:32 p.m.