Triple

T36402021
Position Surface form Disambiguated ID Type / Status
Subject Halocarpus E896655 entity
Predicate hasCommercialValue P74963 FINISHED
Object true 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: true | Statement: [Halocarpus, hasCommercialValue, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCommercialValue
Context triple: [Halocarpus, hasCommercialValue, true]
  • A. hasCommercialFunction
    Indicates that an entity serves a commercial role or purpose, such as engaging in trade, sales, or other profit-oriented activities.
  • B. hasCommercialAppeal
    Indicates that something possesses qualities likely to attract buyers or generate profitable market interest.
  • C. hasCommercialField
    Indicates that one entity possesses or is associated with a commercial-related field, area, or domain in relation to another entity.
  • D. hasCommercialImportance chosen
    Indicates that something possesses economic or business value significant enough to impact trade, revenue, or market activity.
  • E. hasCommercialCore
    Indicates that an entity possesses or includes a central area or component primarily dedicated to commercial activities or functions.
  • 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_69f76e53b81081908d3b81860593f38a completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_6a037c8d06cc8190ab6a5e18d9d2571e completed May 12, 2026, 7:16 p.m.
PD Predicate disambiguation batch_6a037a0a54cc8190868c1bfa1590d1a6 completed May 12, 2026, 7:05 p.m.
Created at: May 3, 2026, 4:10 p.m.