Triple
T30288996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 7482 |
E770319
|
entity |
| Predicate | definesMediaTypeUsage |
P164339
|
FINISHED |
| Object | application/rdap+json |
—
|
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/rdap+json | Statement: [RFC 7482, definesMediaTypeUsage, application/rdap+json]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesMediaTypeUsage Context triple: [RFC 7482, definesMediaTypeUsage, application/rdap+json]
-
A.
definesMediumType
Indicates that one entity specifies or assigns the medium type or format category of another entity.
-
B.
ownedMediaType
Indicates the type or category of media content that is owned in the context of the ownership relationship.
-
C.
definesMessageType
Indicates that one entity specifies or determines the message type classification or category for another entity.
-
D.
attributeUsageTargets
chosen
Indicates that a particular attribute is intended to be applied to, or is valid for use with, specific kinds of targets or elements.
-
E.
definesType
Indicates that one entity specifies or establishes the type or classification of another entity.
- 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_69f224875c288190a9b96b975006ec4a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: April 29, 2026, 7:47 p.m.