Triple

T28776402
Position Surface form Disambiguated ID Type / Status
Subject Mansfield Park estate E726544 entity
Predicate wealthSourceOfOwner P8003 FINISHED
Object Antigua plantations 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: Antigua plantations | Statement: [Mansfield Park estate, wealthSourceOfOwner, Antigua plantations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: wealthSourceOfOwner
Context triple: [Mansfield Park estate, wealthSourceOfOwner, Antigua plantations]
  • A. hasWealthSource
    Indicates that an entity derives its wealth or financial resources from a specified source.
  • B. wealthSource chosen
    Indicates the relationship by which an entity obtains or derives its wealth from a particular source.
  • C. beneficialOwner
    Indicates that one entity is the ultimate beneficiary of ownership rights or economic interest in another entity or asset, even if the ownership is held indirectly or through intermediaries.
  • D. ultimateOwnerOf
    Indicates that one entity is the final, controlling owner of another entity, either directly or through one or more intermediate ownership layers.
  • E. nameBearerWealthSource
    Indicates that the bearer of a particular name derives or is associated with a specific source of wealth.
  • 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_69f03199997c8190b6ae43fb19312443 completed April 28, 2026, 4:03 a.m.
NER Named-entity recognition batch_69f658ee40088190b71e1219407690d0 completed May 2, 2026, 8:05 p.m.
PD Predicate disambiguation batch_69f65760fd3081908ffe014a5e2bf069 completed May 2, 2026, 7:58 p.m.
Created at: April 28, 2026, 6:18 a.m.