Triple

T23954368
Position Surface form Disambiguated ID Type / Status
Subject Uncle Rudolf E603740 entity
Predicate drivesConflictType P154493 FINISHED
Object family inheritance dispute 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: family inheritance dispute | Statement: [Uncle Rudolf, drivesConflictType, family inheritance dispute]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: drivesConflictType
Context triple: [Uncle Rudolf, drivesConflictType, family inheritance dispute]
  • A. triggersConflict
    Indicates that one entity initiates or causes a dispute, clash, or incompatibility to arise with another entity or within a system.
  • B. featuresConflictType
    Indicates that there is a specific type or category of conflict between the features or characteristics of the related entities.
  • C. usedInConflictType
    Indicates that something (such as a resource, method, or capability) is employed or applied within a specific type or category of conflict.
  • D. conflictWith
    Indicates that two entities are in opposition or disagreement, such that their goals, actions, or states are incompatible or interfere with each other.
  • E. conflictType
    Indicates the specific kind or category of conflict that characterizes the relationship or interaction between entities.
  • 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_69e2954222288190a7323554d0cca8d7 completed April 17, 2026, 8:17 p.m.
NER Named-entity recognition batch_69f1d0d616ec81908c796894f40f3015 completed April 29, 2026, 9:35 a.m.
PD Predicate disambiguation batch_69f1615518088190a206f54e2fdb14a3 completed April 29, 2026, 1:39 a.m.
PDg Predicate description generation batch_69f16e348b548190b76e50f9b611f76d completed April 29, 2026, 2:34 a.m.
Created at: April 17, 2026, 9:21 p.m.