Triple

T7533477
Position Surface form Disambiguated ID Type / Status
Subject RDF 1.1 Semantics E178085 entity
Predicate defines P264 FINISHED
Object RDFS entailment 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 entailment | Statement: [RDF 1.1 Semantics, defines, RDFS entailment]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RDFS entailment
Context triple: [RDF 1.1 Semantics, defines, RDFS entailment]
  • A. RDFS chosen
    RDFS (RDF Schema) is a semantic web vocabulary language used to define the structure, classes, and properties of RDF data.
  • B. OWL 2 RL
    OWL 2 RL is a profile of the Web Ontology Language designed for scalable reasoning using rule-based systems, enabling efficient inference over large datasets.
  • 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 2 Full
    OWL 2 Full is a highly expressive semantic web ontology language variant that fully integrates OWL with RDF, allowing powerful but undecidable reasoning over web data.
  • E. OWL 2 DL
    OWL 2 DL is a highly expressive yet decidable description logic–based profile of the OWL 2 Web Ontology Language, designed to balance rich modeling capabilities with computational completeness and decidability.
  • 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_69c84f0765b48190b8df68f22c8901f4 completed March 28, 2026, 9:58 p.m.
Created at: March 27, 2026, 3:47 p.m.