Triple

T29866701
Position Surface form Disambiguated ID Type / Status
Subject glTF E758479 entity
Predicate specificationUrl P5374 FINISHED
Object https://github.com/KhronosGroup/glTF 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: https://github.com/KhronosGroup/glTF | Statement: [glTF, specificationUrl, https://github.com/KhronosGroup/glTF]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: specificationUrl
Context triple: [glTF, specificationUrl, https://github.com/KhronosGroup/glTF]
  • A. specificationLeakedIn
    Indicates that the details or specifications of something have been disclosed or exposed within a particular context, location, or medium without proper authorization.
  • B. hasBrandWebsite
    Indicates that an entity has an associated official website representing its brand.
  • C. primarySpecification
    Indicates that one specification is the main or authoritative specification associated with an entity, distinguishing it from any secondary or supplementary specifications.
  • D. openSpecificationPublishedBy
    Indicates that an open specification has been formally published or issued by a particular entity.
  • E. hasSpecification chosen
    Indicates that an entity is associated with a particular specification that defines or constrains its properties, behavior, or requirements.
  • 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_69f2245b4dec8190b85f664d918a00a5 completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_69f71996e1a48190ac59a1d66d7c44e8 completed May 3, 2026, 9:47 a.m.
PD Predicate disambiguation batch_69f71820c6c88190ab38b4fa626d22cc completed May 3, 2026, 9:40 a.m.
Created at: April 29, 2026, 5:51 p.m.