Triple

T7115477
Position Surface form Disambiguated ID Type / Status
Subject OWL 2 recommendation E165806 entity
Predicate conformsTo P3994 FINISHED
Object RDFS E29939 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: RDFS | Statement: [OWL 2 recommendation, conformsTo, RDFS]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RDFS
Context triple: [OWL 2 recommendation, conformsTo, RDFS]
  • A. RDFS chosen
    RDFS (RDF Schema) is a semantic web vocabulary language used to define the structure, classes, and properties of RDF data.
  • 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 Semantics
    RDF 1.1 Semantics is a W3C specification that formally defines the meaning and logical foundations of RDF data, enabling consistent interpretation and reasoning across RDF graphs.
  • D. OWL
    OWL (Web Ontology Language) is a W3C-recommended semantic web language used to define and share rich, machine-interpretable ontologies on the web.
  • E. RDF 1.1 Concepts and Abstract Syntax
    RDF 1.1 Concepts and Abstract Syntax is a W3C specification that defines the core data model, terminology, and abstract syntax for the Resource Description Framework (RDF).
  • 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_69c6888227bc8190a1394679e3116f90 completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6e5f401b881909ef4c2ab1e0750db completed March 27, 2026, 8:17 p.m.
NED1 Entity disambiguation (via context triple) batch_69c79cbfc7a08190ab07f3d65aa79f16 completed March 28, 2026, 9:17 a.m.
Created at: March 27, 2026, 2:43 p.m.