Triple

T18566400
Position Surface form Disambiguated ID Type / Status
Subject IFRS Conceptual Framework for Financial Reporting E453769 entity
Predicate identifiesPrimaryUsers P63093 FINISHED
Object existing and potential investors 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: existing and potential investors | Statement: [IFRS Conceptual Framework for Financial Reporting, identifiesPrimaryUsers, existing and potential investors]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: identifiesPrimaryUsers
Context triple: [IFRS Conceptual Framework for Financial Reporting, identifiesPrimaryUsers, existing and potential investors]
  • A. speciesOfPrimaryUser
    Indicates the biological species to which the primary user of something (e.g., a device, service, or resource) belongs.
  • B. primaryUsersRole
    Indicates the role that a primary user holds in relation to a given resource, system, or context.
  • C. primaryUserGroups
    Indicates the main or default user groups to which an entity (such as a user account) is assigned.
  • D. primaryAllianceUsers
    Indicates that the subject entity has users who are designated as primary members or participants within an alliance or allied group.
  • E. primaryUserType chosen
    Indicates the main or dominant category of user associated with an entity or interaction.
  • 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_69d8d38974308190a9174430ef256b73 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e53aff027481909ca7257967967650 completed April 19, 2026, 8:28 p.m.
PD Predicate disambiguation batch_69e478c16e0c8190b03966aa23c395a6 completed April 19, 2026, 6:40 a.m.
Created at: April 10, 2026, 11:43 a.m.