Triple

T26721902
Position Surface form Disambiguated ID Type / Status
Subject SR 100 E673726 entity
Predicate isNonUniqueIdentifier P116230 FINISHED
Object yes 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: yes | Statement: [SR 100, isNonUniqueIdentifier, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isNonUniqueIdentifier
Context triple: [SR 100, isNonUniqueIdentifier, yes]
  • A. isNonUniqueGlobally chosen
    Indicates that the referenced item is not guaranteed to be unique across the entire global scope or system.
  • B. isUniqueWithinSystem
    Indicates that an entity exists only once and has no duplicates within the defined system or scope.
  • C. isUniqueWithinStandard
    Indicates that an entity is the only one of its kind within the scope or constraints of a given standard or specification.
  • D. isUniqueTo
    Indicates that a property, characteristic, or association belongs exclusively to a particular entity and is not shared with any other.
  • E. isUniqueWithinScheme
    Indicates that an entity is the only one with its particular identifying characteristics within a given scheme or classification system.
  • 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_69eecda481d08190aea69f2f7c745f56 completed April 27, 2026, 2:44 a.m.
NER Named-entity recognition batch_69f6352fdb788190b9bad30243690743 completed May 2, 2026, 5:32 p.m.
PD Predicate disambiguation batch_69f631850ae08190a0ba51e4f1e4ccb3 completed May 2, 2026, 5:16 p.m.
Created at: April 27, 2026, 3:41 a.m.