Triple

T34746904
Position Surface form Disambiguated ID Type / Status
Subject Mitrastemonaceae E1001660 entity
Predicate visiblePlantPart P51054 FINISHED
Object emergent reproductive structures on forest floor 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: emergent reproductive structures on forest floor | Statement: [Mitrastemonaceae, visiblePlantPart, emergent reproductive structures on forest floor]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: visiblePlantPart
Context triple: [Mitrastemonaceae, visiblePlantPart, emergent reproductive structures on forest floor]
  • A. hasPlantPart chosen
    Indicates that one entity includes, contains, or is composed of a specific plant part of another entity.
  • B. affectsPlantPart
    Indicates that one entity produces an influence, change, or impact on a specific part of a plant.
  • C. isGrowingPartOf
    Indicates that one entity is an expanding or developing component within the larger whole represented by another entity.
  • D. involvesPlant
    Indicates that the relationship or action includes or pertains to a plant as a participating entity.
  • E. hostsPlantOf
    Indicates that one entity serves as a host environment or substrate on which a particular plant lives, grows, or depends.
  • 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_69f76db0367081909b57c50a7fb03025 completed May 3, 2026, 3:45 p.m.
NER Named-entity recognition batch_69f77ffa6b68819090257fed3802c239 completed May 3, 2026, 5:03 p.m.
PD Predicate disambiguation batch_69f7795978c481909e152cd1bd02dd07 completed May 3, 2026, 4:35 p.m.
Created at: May 3, 2026, 3:59 p.m.