Triple

T25402206
Position Surface form Disambiguated ID Type / Status
Subject coining the term "Dinosauria" E636453 entity
Predicate basedOnGenera P7125 FINISHED
Object Megalosaurus 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: Megalosaurus | Statement: [coining the term "Dinosauria", basedOnGenera, Megalosaurus]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: basedOnGenera
Context triple: [coining the term "Dinosauria", basedOnGenera, Megalosaurus]
  • A. basedOnBy
    Indicates that one entity is derived from, justified by, or constructed using another entity as its source, foundation, or reference.
  • B. hasGenera
    Indicates a taxonomic relationship in which a higher-level group (such as a family or subfamily) includes one or more genera as its subordinate members.
  • C. basedOnFamilyOf
    Indicates that one entity is derived from, modeled after, or determined by the family, lineage, or familial characteristics of another entity.
  • D. isBasedOn chosen
    Indicates that one entity is derived from, inspired by, or developed using the content, structure, or principles of another entity.
  • E. recognizedGenera
    Indicates that one entity formally acknowledges or accepts another entity as a valid genus within a taxonomic or classificatory system.
  • 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_69e75db361d881908d8701c856da6413 completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f650c70d7c819093d9a0f005f7c8d5 completed May 2, 2026, 7:30 p.m.
PD Predicate disambiguation batch_69f64cab1f648190a2a9460690d18a37 completed May 2, 2026, 7:12 p.m.
Created at: April 21, 2026, 1:52 p.m.