Triple
T24143006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO/IEC 8859-10 |
E598294
|
entity |
| Predicate | registeredMIMEName |
P71607
|
FINISHED |
| Object | ISO-8859-10 |
—
|
NE NERFINISHED |
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: ISO-8859-10 | Statement: [ISO/IEC 8859-10, registeredMIMEName, ISO-8859-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registeredMIMEName Context triple: [ISO/IEC 8859-10, registeredMIMEName, ISO-8859-10]
-
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.
ownedMediaType
Indicates the type or category of media content that is owned in the context of the ownership relationship.
-
E.
mediaTypeRecognized
Indicates that a system has successfully identified and accepted the type or format of a given media item as valid or supported.
- 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_69e288c92e448190ac57034fa0c863ce |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e00832148190b40b904d514a286b |
completed | April 29, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:28 p.m.