Triple

T21860
Position Surface form Disambiguated ID Type / Status
Subject Carnegie United Kingdom Trust E434 entity
Predicate hasBeneficiary P379 FINISHED
Object people in the United Kingdom 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: people in the United Kingdom | Statement: [Carnegie United Kingdom Trust, hasBeneficiary, people in the United Kingdom]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasBeneficiary
Context triple: [Carnegie United Kingdom Trust, hasBeneficiary, people in the United Kingdom]
  • A. hasBank
    Indicates that one entity possesses, is associated with, or is served by a particular bank (such as a financial institution or river bank).
  • B. benefitedCountry
    Indicates that one country gains an advantage, profit, or positive outcome from an action, event, or entity associated with another.
  • C. hasTypeOfRecipient chosen
    Indicates that an entity is associated with a specific category or kind of recipient it is intended for or directed to.
  • D. hasFinancialInstitution
    Indicates that one entity is associated with or linked to a financial institution, such as a bank or similar financial service provider.
  • E. hasPartner
    Indicates that one entity is in a partner relationship (such as romantic, life, or business partnership) with another entity.
  • 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_69a243b4ac2c8190b93c303df797b7b2 completed Feb. 28, 2026, 1:24 a.m.
NER Named-entity recognition batch_69a246e94ca881908f7a7d2c0b293033 completed Feb. 28, 2026, 1:37 a.m.
PD Predicate disambiguation batch_69a24654724481909ba14b7f68d2a472 completed Feb. 28, 2026, 1:35 a.m.
Created at: Feb. 28, 2026, 1:34 a.m.