Triple
T1413094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ken Thompson |
E31846
|
entity |
| Predicate | notableWork |
P4
|
FINISHED |
| Object | UTF-8 |
E162096
|
NE 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: UTF-8 | Statement: [Ken Thompson, notableWork, UTF-8]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: UTF-8 Context triple: [Ken Thompson, notableWork, UTF-8]
-
A.
UTF-8
chosen
UTF-8 is a widely used variable-length character encoding standard for Unicode that efficiently represents text in most of the world's writing systems while maintaining backward compatibility with ASCII.
-
B.
Unicode
Unicode is a universal character encoding standard that assigns unique code points to virtually all written scripts, symbols, and emojis used in modern computing.
-
C.
UTF-7
UTF-7 is an obsolete, 7-bit Unicode text encoding designed primarily for safe transmission of Unicode data over email systems that were not fully 8-bit clean.
-
D.
UTF-32
UTF-32 is a fixed-length Unicode character encoding that represents each code point using 32 bits, providing simple indexing at the cost of higher memory usage.
-
E.
ASCII
ASCII is a widely used character encoding standard that represents text in computers and other devices using 7-bit numerical codes for letters, digits, punctuation, and control characters.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a49919a994819086528951bc224775 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3e476f08190aed1576805c62462 |
completed | March 1, 2026, 10:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad015a52a88190933e7337067e5364 |
completed | March 8, 2026, 4:55 a.m. |
Created at: March 1, 2026, 7:59 p.m.