Triple
T7563455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RDF 1.1 XML Syntax |
E178848
|
entity |
| Predicate | definesMediaType |
P55167
|
FINISHED |
| Object | application/rdf+xml |
—
|
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: application/rdf+xml | Statement: [RDF 1.1 XML Syntax, definesMediaType, application/rdf+xml]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesMediaType Context triple: [RDF 1.1 XML Syntax, definesMediaType, application/rdf+xml]
-
A.
hasMediaTypeRecognized
Indicates that the media type of an item has been successfully identified and acknowledged as valid or known.
-
B.
definesMessageType
Indicates that one entity specifies or determines the message type classification or category for another entity.
-
C.
definesType
Indicates that one entity specifies or establishes the type or classification of another entity.
-
D.
mediaType
Indicates the format or category of media associated with an entity, such as text, image, audio, or video.
-
E.
typicalMIMEType
chosen
Indicates the standard or most commonly used MIME (media) type associated with a given resource or format.
- 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_69c69f2f80288190b95cceb4da92ab2b |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8fb1c00819096bdb73334d8d72e |
completed | March 27, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69c6f4dc485c819080da13e3b7f4f08f |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:50 p.m.