Triple

T7707847
Position Surface form Disambiguated ID Type / Status
Subject Phoenix E174666 entity
Predicate lifecycleFeature P78261 FINISHED
Object lives for many centuries before burning 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: lives for many centuries before burning | Statement: [Phoenix, lifecycleFeature, lives for many centuries before burning]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: lifecycleFeature
Context triple: [Phoenix, lifecycleFeature, lives for many centuries before burning]
  • A. featureFlag
    Indicates that a particular functionality or behavior is conditionally enabled or disabled for an entity based on a configurable flag.
  • B. facadeFeature
    Indicates that one element functions as a distinct architectural or design feature on the façade of another structure.
  • C. laterFeature
    Indicates that one feature, event, or element occurs or is introduced after another in time.
  • D. isFeatureBased
    Indicates that one entity is derived from, determined by, or constructed using the characteristics or attributes of another entity.
  • E. designedFeature
    Indicates that one entity is a feature or component intentionally planned, created, or specified by another entity as part of a design.
  • F. None of above. chosen

Provenance (4 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_69c6995b3e8c8190833108f883d5f53c completed March 27, 2026, 2:51 p.m.
NER Named-entity recognition batch_69c702ebb7448190ae8d47fe0cbb0907 completed March 27, 2026, 10:21 p.m.
PD Predicate disambiguation batch_69c701683dec8190be9861e592aa8ce0 completed March 27, 2026, 10:15 p.m.
PDg Predicate description generation batch_69c702e9a32081909a153190a62af426 completed March 27, 2026, 10:21 p.m.
Created at: March 27, 2026, 4:04 p.m.