Triple

T33477966
Position Surface form Disambiguated ID Type / Status
Subject Longbourn estate E857377 entity
Predicate entailLimitsInheritanceTo P99 FINISHED
Object male heir 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: male heir | Statement: [Longbourn estate, entailLimitsInheritanceTo, male heir]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: entailLimitsInheritanceTo
Context triple: [Longbourn estate, entailLimitsInheritanceTo, male heir]
  • A. losesInheritanceThrough
    Indicates that one party forfeits or is disqualified from receiving an inheritance as a consequence of another specified party or condition.
  • B. isLimitOf
    Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
  • C. isPartiallyLimitedBy
    Indicates that one entity’s extent, effect, or behavior is constrained to some degree—but not completely—by another entity.
  • D. hasLimitation chosen
    Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
  • E. inheritanceStatus
    Indicates the type or condition of inheritance rights or succession status that applies between related parties.
  • 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_69f3497472508190b300ebd3fd402367 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6e52c1a848190b35743f9e5361969 completed May 3, 2026, 6:03 a.m.
PD Predicate disambiguation batch_69f6e3da41948190a4cfe866ce184f73 completed May 3, 2026, 5:57 a.m.
Created at: May 1, 2026, 1:38 a.m.