Triple
T34487840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIXER |
E885379
|
entity |
| Predicate | usesForContentEncoding |
P64032
|
FINISHED |
| Object | MIME content types |
—
|
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: MIME content types | Statement: [MIXER, usesForContentEncoding, MIME content types]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesForContentEncoding Context triple: [MIXER, usesForContentEncoding, MIME content types]
-
A.
usesEncodingRules
Indicates that one entity applies or conforms to a specified set of encoding rules when representing or transforming information.
-
B.
differenceFromContentEncoding
Indicates that one encoding or representation of content differs from another specified content encoding.
-
C.
usesEncoder
Indicates that one entity employs or relies on an encoder component or mechanism to perform its function or process data.
-
D.
usesCodec
chosen
Indicates that one entity employs or relies on a specific codec to encode, decode, or process data.
-
E.
usesDifferentialEncoding
Indicates that one entity applies differential encoding techniques to represent or transmit information relative to changes rather than absolute values.
- 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_69f349c947fc81909d30b53c194d6ea1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: May 1, 2026, 2:01 a.m.