Triple
T24174797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO/IEC 8859-16 |
E599248
|
entity |
| Predicate | encodingFamily |
P20982
|
FINISHED |
| Object | ISO 8-bit character sets |
—
|
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 8-bit character sets | Statement: [ISO/IEC 8859-16, encodingFamily, ISO 8-bit character sets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encodingFamily Context triple: [ISO/IEC 8859-16, encodingFamily, ISO 8-bit character sets]
-
A.
codingSystemType
chosen
Indicates the classification or category of coding system used to encode or represent information in a given context.
-
B.
languageFamily
Indicates that two or more languages belong to the same genealogical language family or linguistic lineage.
-
C.
syntaxFamily
Indicates that two linguistic elements share a common syntactic type, pattern, or structural classification within a grammar system.
-
D.
languageFamilyCode
Indicates the language family to which a given language belongs, represented by a standardized code.
-
E.
encodingIndependence
Indicates that a relationship or property holds regardless of the specific encoding or representation used for the involved entities.
- 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.