Triple
T7422996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RIF |
E171294
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | RDF |
E29602
|
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 | Statement: [RIF, relatedTo, RDF]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RDF Context triple: [RIF, 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.
RDFa
RDFa is a W3C-recommended syntax for embedding structured, machine-readable metadata within HTML and other web documents using attributes.
-
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_69c68a625d048190af70eb8b63bec5a0 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2eece588190905774e7151edcb8 |
completed | March 27, 2026, 9:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8277f749c8190a91f620c71c48433 |
completed | March 28, 2026, 7:09 p.m. |
Created at: March 27, 2026, 3:12 p.m.