Triple
T32378504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Server-Sent Events |
E827349
|
entity |
| Predicate | defaultMIMEType |
P55167
|
FINISHED |
| Object | text/event-stream |
—
|
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: text/event-stream | Statement: [Server-Sent Events, defaultMIMEType, text/event-stream]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultMIMEType Context triple: [Server-Sent Events, defaultMIMEType, text/event-stream]
-
A.
typicalMIMEType
chosen
Indicates the standard or most commonly used MIME (media) type associated with a given resource or format.
-
B.
mediaType
Indicates the format or category of media associated with an entity, such as text, image, audio, or video.
-
C.
typicalFileType
Indicates that one entity is the usual or commonly associated file type for the other entity.
-
D.
mediaTypeRecognized
Indicates that a system has successfully identified and accepted the type or format of a given media item as valid or supported.
-
E.
defaultPackageFormat
Indicates the standard or primary packaging format that is used by default for an item or distribution.
- 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_69f349177ddc8190ab0583f05597056b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 1, 2026, 12:51 a.m.