Triple

T10213688
Position Surface form Disambiguated ID Type / Status
Subject Ginkgoales E242390 entity
Predicate knownFromFossilRecord P9689 FINISHED
Object true 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: true | Statement: [Ginkgoales, knownFromFossilRecord, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: knownFromFossilRecord
Context triple: [Ginkgoales, knownFromFossilRecord, true]
  • A. fossilRecordExtendsBackTo
    Indicates that the existence or presence of something is documented in the fossil record as originating from a specified time or geological period.
  • B. containsFossilsOf chosen
    Indicates that one entity (typically a geological formation, rock, or sample) includes fossil remains or traces belonging to another entity (an organism or taxon).
  • C. fossilRecordStatus
    Indicates the preservation state or condition of an organism’s remains as documented in the fossil record.
  • D. fossilRangeQualifier
    Indicates how the temporal range of a fossil (e.g., its first or last appearance in the geologic record) should be interpreted, refined, or qualified.
  • E. geologicRecord
    Indicates that one entity serves as a geologic record documenting the history, processes, or conditions of another entity over time.
  • 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_69d381ae26c48190985abd0e25ee5d04 completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d3aa24efc081909714d98943543283 completed April 6, 2026, 12:42 p.m.
PD Predicate disambiguation batch_69d39559e5ac8190b88eca75956b7e6a completed April 6, 2026, 11:13 a.m.
Created at: April 6, 2026, 11:03 a.m.