Triple

T7533533
Position Surface form Disambiguated ID Type / Status
Subject RDF 1.0 E178086 entity
Predicate hasComponent P35 FINISHED
Object RDF Schema 1.0 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: RDF Schema 1.0 | Statement: [RDF 1.0, hasComponent, RDF Schema 1.0]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RDF Schema 1.0
Context triple: [RDF 1.0, hasComponent, RDF Schema 1.0]
  • A. RDF 1.0
    RDF 1.0 is the original W3C standard model for representing information about web resources using subject–predicate–object triples.
  • 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 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).
  • D. RDFS chosen
    RDFS (RDF Schema) is a semantic web vocabulary language used to define the structure, classes, and properties of RDF data.
  • E. 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.
  • 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_69c69f2acdbc8190b5a8320168c1d0ba completed March 27, 2026, 3:15 p.m.
NER Named-entity recognition batch_69c6f8493964819086aeddfa4872a70b completed March 27, 2026, 9:36 p.m.
NED1 Entity disambiguation (via context triple) batch_69c856b369c88190b8a9a196e2166f9f completed March 28, 2026, 10:31 p.m.
Created at: March 27, 2026, 3:47 p.m.