Triple

T1390350
Position Surface form Disambiguated ID Type / Status
Subject RDFS E29939 entity
Predicate hasSpecificationDocument P5374 FINISHED
Object RDF Schema 1.1 E29939 NE FINISHED

How this triple was built (3 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.1 | Statement: [RDFS, hasSpecificationDocument, RDF Schema 1.1]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: RDF Schema 1.1
Context triple: [RDFS, hasSpecificationDocument, RDF Schema 1.1]
  • 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. OWL
    OWL (Web Ontology Language) is a W3C-recommended semantic web language used to define and share rich, machine-interpretable ontologies on the web.
  • D. OWL Full
    OWL Full is the most expressive and semantically unrestricted variant of the Web Ontology Language, allowing full RDF compatibility at the cost of computational decidability.
  • E. OWL 2 QL
    OWL 2 QL is a lightweight profile of the Web Ontology Language designed to enable efficient query answering over large datasets using standard relational database technologies.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
PD Predicate disambiguation gpt-5-mini-2025-08-07 
Target predicate: hasSpecificationDocument
Context triple: [RDFS, hasSpecificationDocument, RDF Schema 1.1]
  • A. hasSpecification chosen
    Indicates that an entity is associated with a particular specification that defines or constrains its properties, behavior, or requirements.
  • B. hasOfficialDocument
    Indicates that an entity possesses or is associated with a formal, authorized document issued by a recognized authority.
  • C. regulatoryDocument
    Indicates a relationship where one entity serves as a regulatory document that defines rules, standards, or requirements governing another entity.
  • D. institutedByDocument
    Indicates that something (such as a rule, organization, or status) is formally established or created by a specific document.
  • E. hasLegalInstrument
    Indicates that there exists a formal legal document or instrument that establishes, governs, or records the relationship between the related entities.
  • F. None of above.

Provenance (4 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_69a498dc92f8819094a1108f8ac90f43 completed March 1, 2026, 7:51 p.m.
NER Named-entity recognition batch_69a4c35e023c8190b45688796d90534b completed March 1, 2026, 10:53 p.m.
NED1 Entity disambiguation (via context triple) batch_69ad0153f1648190abd63beadfb6709b completed March 8, 2026, 4:55 a.m.
PD Predicate disambiguation batch_69a4beffcf808190ab4cd0271257ce63 completed March 1, 2026, 10:34 p.m.
Created at: March 1, 2026, 7:59 p.m.