Triple
T19276838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unicode 5.2 |
E482078
|
entity |
| Predicate | hasTechnicalReport |
P5712
|
FINISHED |
| Object | Unicode Technical Report #17 (Unicode Character Encoding Model, updated for 5.2) |
—
|
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: Unicode Technical Report #17 (Unicode Character Encoding Model, updated for 5.2) | Statement: [Unicode 5.2, hasTechnicalReport, Unicode Technical Report #17 (Unicode Character Encoding Model, updated for 5.2)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Unicode Technical Report #17 (Unicode Character Encoding Model, updated for 5.2) Context triple: [Unicode 5.2, hasTechnicalReport, Unicode Technical Report #17 (Unicode Character Encoding Model, updated for 5.2)]
-
A.
The Unicode Standard
The Unicode Standard is a universal character encoding system that assigns unique code points to text and symbols from virtually all writing systems, enabling consistent digital representation and interchange of written language worldwide.
-
B.
Unicode Technical Report #29
Unicode Technical Report #29 is the specification that defines how to determine and segment user-perceived text elements (grapheme clusters), words, and sentences in Unicode text.
-
C.
Unicode Technical Reports
chosen
Unicode Technical Reports are supplementary documents published by the Unicode Consortium that provide detailed guidance, algorithms, and clarifications on specific aspects of Unicode beyond what is covered in the core specification.
-
D.
Unicode Technical Standard #10
Unicode Technical Standard #10 is the specification that defines the Unicode Collation Algorithm, providing a standardized method for comparing and sorting Unicode text across languages and platforms.
-
E.
Unicode pre-1.0 draft specifications
Unicode pre-1.0 draft specifications were early, provisional versions of the Unicode character encoding standard that defined its initial design and repertoire before the formal release of Unicode 1.0.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fbbd5f34819086535f28fd880411 |
completed | April 20, 2026, 10:11 a.m. |
Created at: April 10, 2026, 1:29 p.m.