Triple
T6581269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windows-1252 |
E157300
|
entity |
| Predicate | IANACharsetName |
P58058
|
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-1252, IANACharsetName, windows-1252]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IANACharsetName Context triple: [Windows-1252, IANACharsetName, windows-1252]
-
A.
usesCharacterSet
Indicates that one entity employs or relies on a specific character set defined by another entity for encoding or representing text.
-
B.
ISOBasicLatinDerivative
Indicates that one entity is a derivative or variant form of another entity within the ISO Basic Latin character set.
-
C.
hasUnicodeName
Indicates that an entity is associated with a specific official Unicode name assigned to a character or symbol.
-
D.
characterSetName
Indicates the name assigned to a particular character set used for encoding or representing characters.
-
E.
hasMIMECharsetName
chosen
Indicates that an entity (such as a character encoding) is associated with a specific MIME charset name used in internet protocols.
- 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_69c6882b3a108190b3a9eb343ae4162c |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6c07cdf048190945ca5810fb1de88 |
completed | March 27, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c6acfb462481909cb7aff5af4bca9d |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:54 p.m.