Triple

T10329237
Position Surface form Disambiguated ID Type / Status
Subject Open Web Platform E242834 entity
Predicate hasComponent P35 FINISHED
Object RDFa in HTML E171236 NE 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: RDFa in HTML | Statement: [Open Web Platform, hasComponent, RDFa in HTML]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RDFa in HTML
Context triple: [Open Web Platform, hasComponent, RDFa in HTML]
  • A. RDFa chosen
    RDFa is a W3C-recommended syntax for embedding structured, machine-readable metadata within HTML and other web documents using attributes.
  • B. RDF
    RDF (Resource Description Framework) is a standard model for data interchange on the Web that represents information as subject–predicate–object triples to enable structured, machine-readable metadata and knowledge graphs.
  • C. RDF 1.1 family of specifications
    The RDF 1.1 family of specifications is a standardized set of W3C recommendations that define how to represent, store, and exchange structured data on the Web using the Resource Description Framework.
  • D. RDF 1.1 XML Syntax
    RDF 1.1 XML Syntax is a W3C specification that defines how RDF data is represented and serialized using XML.
  • E. RDF 1.0
    RDF 1.0 is the original W3C standard model for representing information about web resources using subject–predicate–object triples.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d381af787481908bc401325c760a88 completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4d7cfd54c8190b6f88598339536d1 completed April 7, 2026, 10:09 a.m.
NED1 Entity disambiguation (via context triple) batch_69d71db4a8dc81909adb2a044e74fd6b completed April 9, 2026, 3:32 a.m.
Created at: April 6, 2026, 11:52 a.m.