Triple
T24151154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO/IEC 8859-14 |
E598535
|
entity |
| Predicate | mappedInto |
P146408
|
FINISHED |
| Object | Unicode code points |
—
|
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: Unicode code points | Statement: [ISO/IEC 8859-14, mappedInto, Unicode code points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mappedInto Context triple: [ISO/IEC 8859-14, mappedInto, Unicode code points]
-
A.
mappedUsing
Indicates that one entity is associated or transformed into another entity through a specified mapping method or mechanism.
-
B.
mapped
Indicates that one entity has been associated, corresponded, or linked systematically to another according to some defined mapping or alignment.
-
C.
mappingTarget
chosen
Indicates that one entity serves as the destination or result of a mapping defined from another entity.
-
D.
mappingBy
Indicates that one entity is related to another through a defined mapping or association, specifying which side or field governs the relationship.
-
E.
derivedInto
Indicates that one entity is produced, transformed, or evolved from another as a result of some derivation process.
- 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_69e288c9e488819093dd1acd91b08b8a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e0e108308190ba8740590a1c5130 |
completed | April 29, 2026, 10:43 a.m. |
| PD | Predicate disambiguation | batch_69f176585f3481909beb907de252cd98 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:30 p.m.