Triple

T38447589
Position Surface form Disambiguated ID Type / Status
Subject Stonefoots E906680 entity
Predicate ancestralReputation P116143 FINISHED
Object long-standing Dwarven lineage 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: long-standing Dwarven lineage | Statement: [Stonefoots, ancestralReputation, long-standing Dwarven lineage]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ancestralReputation
Context triple: [Stonefoots, ancestralReputation, long-standing Dwarven lineage]
  • A. ancestralStatus
    Indicates that one entity holds a particular ancestral or lineage-based relationship or status in relation to another entity.
  • B. ancestralLinks
    Indicates a genealogical relationship where one entity is an ancestor of, or connected through a line of descent to, another entity.
  • C. typeOfAncestry chosen
    Indicates that one entity’s ancestry or lineage is characterized as being of a particular type or origin in relation to another entity.
  • D. ancestralDomain
    Indicates that one entity is the traditional or long-held territory or domain from which another entity originates or to which it is ancestrally connected.
  • E. ancestralPlaneAppearance
    Indicates that an entity appears or manifests within an ancestral or spiritual plane in relation to another entity or context.
  • 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_69f76e72878c8190a692836c8b01b58b completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fcce7afcd08190906cc3801152656a completed May 7, 2026, 5:40 p.m.
PD Predicate disambiguation batch_69fcccf140ec8190862d53388a5f40d7 completed May 7, 2026, 5:33 p.m.
Created at: May 3, 2026, 4:31 p.m.