Triple
T24174803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO/IEC 8859-16 |
E599248
|
entity |
| Predicate | usesEncodingModel |
P33682
|
FINISHED |
| Object | single-byte substitution mapping |
—
|
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: single-byte substitution mapping | Statement: [ISO/IEC 8859-16, usesEncodingModel, single-byte substitution mapping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesEncodingModel Context triple: [ISO/IEC 8859-16, usesEncodingModel, single-byte substitution mapping]
-
A.
usesEncoder
Indicates that one entity employs or relies on an encoder component or mechanism to perform its function or process data.
-
B.
dataEncodingMethod
chosen
Indicates the specific technique or format used to encode data for storage, transmission, or processing.
-
C.
localEncoding
Indicates that an entity is represented or stored using a specific encoding scheme that is defined or applied locally within a particular context or system.
-
D.
encodedIn
Indicates that one entity is represented, stored, or expressed within another entity using a specific encoding or format.
-
E.
usesCodec
Indicates that one entity employs or relies on a specific codec to encode, decode, or process data.
- 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_69e288cca05481908faeb1563711114a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:33 p.m.