Triple

T19995998
Position Surface form Disambiguated ID Type / Status
Subject French nobility E494193 entity
Predicate couldBeAcquiredBy P138271 FINISHED
Object inheritance 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: inheritance | Statement: [French nobility, couldBeAcquiredBy, inheritance]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: couldBeAcquiredBy
Context triple: [French nobility, couldBeAcquiredBy, inheritance]
  • A. laterAcquiredBy
    Indicates that one entity was acquired by another entity at a later point in time, after some prior state or ownership.
  • B. acquisitionAnnouncedBy
    Indicates that an acquisition event was publicly announced by the specified announcing entity (such as a company or organization).
  • C. laterAcquiredThrough
    Indicates that one entity came to possess or obtain another entity at a subsequent time specifically by means of a particular acquisition method or process.
  • D. acquiredFor
    Indicates that one entity obtained or purchased another entity specifically for the benefit, use, or purpose of a third entity.
  • E. acquisitionType
    Indicates the specific kind or category of acquisition relationship that exists between entities (such as a company buying another company, assets, or a controlling stake).
  • 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_69da626b2d748190886981ea90c8b2ea completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e65fe3fb288190a935c334e8a5d54e completed April 20, 2026, 5:18 p.m.
PD Predicate disambiguation batch_69e537fd311881908448f2aea8b4812e completed April 19, 2026, 8:15 p.m.
PDg Predicate description generation batch_69e543c42c688190a22f4d31ec692377 completed April 19, 2026, 9:06 p.m.
Created at: April 11, 2026, 3:32 p.m.