Triple

T31769006
Position Surface form Disambiguated ID Type / Status
Subject Greendale study group E810885 entity
Predicate includesElderlyHeir P94705 FINISHED
Object Pierce Hawthorne NE NERFINISHED

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: Pierce Hawthorne | Statement: [Greendale study group, includesElderlyHeir, Pierce Hawthorne]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: includesElderlyHeir
Context triple: [Greendale study group, includesElderlyHeir, Pierce Hawthorne]
  • A. hasElders chosen
    Indicates that one entity has elders, i.e., individuals recognized as senior, guiding, or authoritative figures in relation to it.
  • B. isHeirIn
    Indicates that one entity is the designated heir within or under the inheritance rules of another entity (such as a person, estate, or legal framework).
  • C. isHeirExpectedBy
    Indicates that one entity is anticipated or designated to inherit from, succeed, or receive rights from another entity.
  • D. associatedHeir
    Indicates that one entity is designated or recognized as the heir connected to, or inheriting from, another entity.
  • E. agreedHeir
    Indicates that one entity has been formally designated and accepted as the heir of another, typically through mutual agreement or legal arrangement.
  • 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_69f348e463e08190b902d4819195e1f0 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_6a0174e8b5b481908bf0c6d3d5b0f3b6 completed May 11, 2026, 6:19 a.m.
PD Predicate disambiguation batch_6a01748d65248190ac3d9adfa9d0b274 completed May 11, 2026, 6:17 a.m.
Created at: April 30, 2026, 11:33 p.m.