Triple

T2968194
Position Surface form Disambiguated ID Type / Status
Subject Obsidian (color) E80216 entity
Predicate perceivedQualities P8206 FINISHED
Object elegant 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: elegant | Statement: [Obsidian (color), perceivedQualities, elegant]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: perceivedQualities
Context triple: [Obsidian (color), perceivedQualities, elegant]
  • A. hasPerceptualQuality chosen
    Indicates that something possesses a particular sensory or perceptual characteristic, such as a color, sound, texture, taste, or smell.
  • B. storageQuality
    Indicates the degree or standard of how well something is stored, such as its preservation, safety, or suitability for use.
  • C. influencedPerceptionOf
    Indicates that one entity has affected, shaped, or altered how another entity is perceived or understood.
  • D. quality
    Indicates that an entity possesses a particular attribute, characteristic, or degree of excellence that defines how good, suitable, or effective it is in a given context.
  • E. hasCookingQuality
    Indicates that something possesses a particular characteristic or attribute related to cooking, such as flavor, texture, or suitability for a cooking method.
  • 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_69ad8b14ffe881908ffed62f9595c867 completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad996fa4388190abd319c69ee583d9 completed March 8, 2026, 3:44 p.m.
PD Predicate disambiguation batch_69ad960e71f8819088179d11248c6ed0 completed March 8, 2026, 3:30 p.m.
Created at: March 8, 2026, 2:58 p.m.