Triple

T994358
Position Surface form Disambiguated ID Type / Status
Subject Oracle Fusion Applications E21462 entity
Predicate supportsBusinessFunction P9642 FINISHED
Object enterprise resource planning 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: enterprise resource planning | Statement: [Oracle Fusion Applications, supportsBusinessFunction, enterprise resource planning]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsBusinessFunction
Context triple: [Oracle Fusion Applications, supportsBusinessFunction, enterprise resource planning]
  • A. businessFunction chosen
    Indicates the specific role, activity, or operational function that an entity performs within a business context.
  • B. usesBusinessModel
    Indicates that one entity operates according to, or applies in practice, the business model defined or provided by another entity.
  • C. hasBusiness
    Indicates that one entity owns, operates, or is formally associated with a business entity.
  • D. supportsUse
    Indicates that one entity enables, allows, or is compatible with the use or operation of another entity.
  • E. supportsProduct
    Indicates that one entity provides assistance, compatibility, or necessary resources for the operation, use, or maintenance of a specified product.
  • 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_69a493c476b48190b41fc5e793171cc6 completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4b4c5e16881908cd5f7ba2fcd5084 completed March 1, 2026, 9:51 p.m.
PD Predicate disambiguation batch_69a4b2af071c819086c374a16307dfe0 completed March 1, 2026, 9:42 p.m.
Created at: March 1, 2026, 7:41 p.m.