Triple

T36467434
Position Surface form Disambiguated ID Type / Status
Subject Maplesoft E898457 entity
Predicate hasCommercialUsers P158607 FINISHED
Object engineering companies worldwide 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: engineering companies worldwide | Statement: [Maplesoft, hasCommercialUsers, engineering companies worldwide]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCommercialUsers
Context triple: [Maplesoft, hasCommercialUsers, engineering companies worldwide]
  • A. hasCommercialServices
    Indicates that one entity provides or offers commercial services to another entity or within a specified context.
  • B. hasCommercialCore
    Indicates that an entity possesses or includes a central area or component primarily dedicated to commercial activities or functions.
  • C. hasCommercialProfile
    Indicates that an entity possesses or is associated with a commercial-oriented profile, typically used for business or trade-related purposes.
  • D. hasUsers chosen
    Indicates that an entity is associated with one or more users who use, own, or are linked to it.
  • E. hasCommercialFunction
    Indicates that an entity serves a commercial role or purpose, such as engaging in trade, sales, or other profit-oriented activities.
  • 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_69f76e58ebd88190b75d9b169b59d793 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_6a037c8e2c648190a65fc9c7872861af completed May 12, 2026, 7:16 p.m.
PD Predicate disambiguation batch_6a037a0bf4b88190bdcfae9a14b51f0a completed May 12, 2026, 7:05 p.m.
Created at: May 3, 2026, 4:10 p.m.