Triple
T19703573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Semantic MediaWiki |
E473153
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | RDF |
—
|
NE NERFINISHED |
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 | Statement: [Semantic MediaWiki, relatedTo, RDF]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RDF Context triple: [Semantic MediaWiki, relatedTo, RDF]
-
A.
RDF
chosen
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.
-
B.
RDFS
RDFS (RDF Schema) is a semantic web vocabulary language used to define the structure, classes, and properties of RDF data.
-
C.
RDF 1.0
RDF 1.0 is the original W3C standard model for representing information about web resources using subject–predicate–object triples.
-
D.
RDF Vocabulary Description Language 1.0: RDF Schema
RDF Vocabulary Description Language 1.0: RDF Schema is a W3C specification that provides a basic type system and schema language for defining classes, properties, and relationships in RDF data.
-
E.
RDFa
RDFa is a W3C-recommended syntax for embedding structured, machine-readable metadata within HTML and other web documents using attributes.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e642b8707081908fbf96c989d2d52d |
completed | April 20, 2026, 3:14 p.m. |
Created at: April 10, 2026, 1:46 p.m.