Triple
T29863918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mod_brotli |
E758395
|
entity |
| Predicate | supportsContentTypeFiltering |
P24486
|
FINISHED |
| Object | MIME type |
—
|
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 type | Statement: [mod_brotli, supportsContentTypeFiltering, MIME type]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsContentTypeFiltering Context triple: [mod_brotli, supportsContentTypeFiltering, MIME type]
-
A.
hasContentType
Indicates that an entity is associated with or classified by a specific type of content.
-
B.
governsContentType
Indicates that one entity defines or controls the rules, behavior, or handling associated with a particular content type.
-
C.
hasFilterType
Indicates that an entity is associated with, or constrained by, a specific type or category of filter applied to it.
-
D.
supportsType
chosen
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
E.
describesContentType
Indicates that one entity specifies or characterizes the type or category of content associated with 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 5:50 p.m.