Triple

T14480188
Position Surface form Disambiguated ID Type / Status
Subject Blue Dress A E359081 entity
Predicate hasUniqueness P114357 FINISHED
Object distinct design identity 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: distinct design identity | Statement: [Blue Dress A, hasUniqueness, distinct design identity]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasUniqueness
Context triple: [Blue Dress A, hasUniqueness, distinct design identity]
  • A. typeOfUniqueness
    Indicates that one entity’s uniqueness is characterized, classified, or constrained by the specific kind or mode of uniqueness associated with another entity.
  • B. uniquenessCondition
    Indicates that a specified element, value, or combination of attributes must be unique within a given set, context, or domain, with no duplicates allowed.
  • C. hasUniqueStatus
    Indicates that an entity possesses a status or condition that is distinct and not shared with any other entity in the given context.
  • D. isUniqueTo
    Indicates that a property, characteristic, or association belongs exclusively to a particular entity and is not shared with any other.
  • E. isUniqueWithinStandard
    Indicates that an entity is the only one of its kind within the scope or constraints of a given standard or specification.
  • F. None of above. chosen

Provenance (4 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_69d827966698819082e140837737501d completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de924a576c819098351efabdb779b1 completed April 14, 2026, 7:15 p.m.
PD Predicate disambiguation batch_69de5c487b4c819097803e58dca628a5 completed April 14, 2026, 3:24 p.m.
PDg Predicate description generation batch_69de5fb4de14819092acdecbd201d672 completed April 14, 2026, 3:39 p.m.
Created at: April 10, 2026, 1:20 a.m.