Triple

T23958553
Position Surface form Disambiguated ID Type / Status
Subject Risk Assessment Framework for foundation trusts E603860 entity
Predicate financialArea P2313 FINISHED
Object liquidity 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: liquidity | Statement: [Risk Assessment Framework for foundation trusts, financialArea, liquidity]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: financialArea
Context triple: [Risk Assessment Framework for foundation trusts, financialArea, liquidity]
  • A. fiancee
    Indicates that one person is formally engaged to be married to another person.
  • B. financialBehavior
    Indicates how an entity manages, uses, or responds to money and financial resources in practice.
  • C. economicAspect chosen
    Indicates that something is related to, characterized by, or has implications for economic factors, conditions, or outcomes.
  • D. primaryFinancialIntelligenceUnit
    Indicates that one entity serves as the main or designated financial intelligence unit responsible for receiving, analyzing, and disseminating financial information related to potential illicit activities for another entity or jurisdiction.
  • E. funds
    Indicates that one entity provides financial resources or monetary support to another entity or activity.
  • 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_69e2954222288190a7323554d0cca8d7 completed April 17, 2026, 8:17 p.m.
NER Named-entity recognition batch_69f1d0d85d348190946b578e1a1c3bcc completed April 29, 2026, 9:35 a.m.
PD Predicate disambiguation batch_69f1615518088190a206f54e2fdb14a3 completed April 29, 2026, 1:39 a.m.
Created at: April 17, 2026, 9:22 p.m.