Triple

T768012
Position Surface form Disambiguated ID Type / Status
Subject Digital Object Identifier system E16216 entity
Predicate supportsMetadataStandard P1587 FINISHED
Object DOI metadata kernel 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: DOI metadata kernel | Statement: [Digital Object Identifier system, supportsMetadataStandard, DOI metadata kernel]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsMetadataStandard
Context triple: [Digital Object Identifier system, supportsMetadataStandard, DOI metadata kernel]
  • A. hasMetadata
    Indicates that one entity is associated with descriptive or informational data about another entity.
  • B. usesStandard chosen
    Indicates that one entity adopts, follows, or operates according to a specified standard defined by another entity or reference.
  • C. standardizationStatus
    Indicates the current stage or condition of an entity in a formal standardization process (e.g., proposed, under review, approved, deprecated).
  • D. hasStandardizationBody
    Indicates that an entity is associated with, governed by, or defined by a specific standards-setting organization or authority.
  • E. hasStandardVersion
    Indicates that one entity serves as the official or canonical version of another entity.
  • 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_69a49369a0848190af883934cee3db4c completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a765ba688190ab328bb159583077 completed March 1, 2026, 8:53 p.m.
PD Predicate disambiguation batch_69a4a5074c788190a74fc20ad24e2d26 completed March 1, 2026, 8:43 p.m.
Created at: March 1, 2026, 7:37 p.m.