Triple
T24269465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windows Western European |
E605236
|
entity |
| Predicate | mimeName |
P71607
|
FINISHED |
| Object | windows-1252 |
—
|
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: windows-1252 | Statement: [Windows Western European, mimeName, windows-1252]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mimeName Context triple: [Windows Western European, mimeName, windows-1252]
-
A.
MIMEName
chosen
Indicates the standardized MIME (Multipurpose Internet Mail Extensions) type name associated with a given entity, specifying its media type and subtype for content identification.
-
B.
typicalMIMEType
Indicates the standard or most commonly used MIME (media) type associated with a given resource or format.
-
C.
mediaType
Indicates the format or category of media associated with an entity, such as text, image, audio, or video.
-
D.
filenameType
Indicates the type or category associated with a given filename (e.g., file format, role, or classification).
-
E.
mediaTypeExample
Indicates that something serves as an example or illustrative instance of a particular media type.
- 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_69e2954707dc8190915551eb114cfff6 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28d58666881909f28f4d4f0f7d590 |
completed | April 29, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:07 a.m.