Triple

T17708799
Position Surface form Disambiguated ID Type / Status
Subject Bikenibeu Paeniu E441504 entity
Predicate hasLifespanStatus P31531 FINISHED
Object living person 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: living person | Statement: [Bikenibeu Paeniu, hasLifespanStatus, living person]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLifespanStatus
Context triple: [Bikenibeu Paeniu, hasLifespanStatus, living person]
  • A. hasLifetimeStatus
    Indicates that an entity is associated with a status or condition that applies for the entire duration of its existence.
  • B. hasMeanLifetime
    Indicates the characteristic average time duration for which an entity, state, or condition persists before it decays, ends, or changes.
  • C. supportsLifespan
    Indicates that one entity contributes to maintaining, extending, or enabling the full duration of another entity’s life or functional existence.
  • D. lifecycleStatus chosen
    Indicates the current phase or condition of an entity within its overall lifecycle or progression from creation to termination.
  • E. lifespanType
    Indicates the type or category of lifespan associated with an entity, such as whether it is finite, indefinite, or of a particular defined duration.
  • 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_69d8b9ea20b48190ace88bb46b01e6a9 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e47299cd7881908aac13b84acb61f7 completed April 19, 2026, 6:13 a.m.
PD Predicate disambiguation batch_69e3cde601d4819097903f471f1fe99a completed April 18, 2026, 6:31 p.m.
Created at: April 10, 2026, 10:05 a.m.