Triple

T19673133
Position Surface form Disambiguated ID Type / Status
Subject Telopea E472383 entity
Predicate regenerationStrategy P121846 FINISHED
Object resprouting from lignotuber after fire 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: resprouting from lignotuber after fire | Statement: [Telopea, regenerationStrategy, resprouting from lignotuber after fire]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: regenerationStrategy
Context triple: [Telopea, regenerationStrategy, resprouting from lignotuber after fire]
  • A. regenerationOf
    Indicates that one entity is the renewed, restored, or regrown version of another entity, typically after damage, loss, or degradation.
  • B. regeneratedWhen
    Indicates that an entity is brought back, restored, or recreated at a specific time or under specific conditions.
  • C. regenerationSource chosen
    Indicates that one entity serves as the origin, cause, or provider for the restoration or regrowth of another entity.
  • D. regenerationNumber
    Indicates the specific iteration or cycle count of a repeated regeneration or renewal event associated with an entity.
  • E. regenerationStartedIn
    Indicates that a regeneration process was initiated or began within a specified location, context, or time frame.
  • 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_69d8e514f2e08190ba70a4449519d218 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e6416d61008190af531c6d346d7da1 completed April 20, 2026, 3:08 p.m.
PD Predicate disambiguation batch_69e514eb37b8819091502cc954f70eba completed April 19, 2026, 5:46 p.m.
Created at: April 10, 2026, 1:45 p.m.