Triple
T25602161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R2RML |
E641814
|
entity |
| Predicate | usesIRI |
P162930
|
FINISHED |
| Object | rr: |
—
|
LITERAL 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: rr: | Statement: [R2RML, usesIRI, rr:]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesIRI Context triple: [R2RML, usesIRI, rr:]
-
A.
usesURI
chosen
Indicates that one entity employs or references another entity via a specific Uniform Resource Identifier (URI) as its means of identification or access.
-
B.
useOfTerm
Indicates that one entity employs or applies a specific term or expression in reference to another entity or context.
-
C.
usesTerminologyFrom
Indicates that one entity adopts or incorporates the specialized terms or vocabulary originating from another entity or source.
-
D.
hasURN
Indicates that an entity is associated with a specific Uniform Resource Name (URN) that uniquely identifies it.
-
E.
rdfs:isDefinedBy
Indicates that the subject’s meaning, definition, or specification is provided or formally described by the referenced resource.
- F. None of above.
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_69e75dc60d108190b7e2419e36b0134b |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 21, 2026, 4:31 p.m.