Triple
T4575456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UTF-7 |
E123130
|
entity |
| Predicate | definedFor |
P4464
|
FINISHED |
| Object | Unicode 1.1 |
E235101
|
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: Unicode 1.1 | Statement: [UTF-7, definedFor, Unicode 1.1]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Unicode 1.1 Context triple: [UTF-7, definedFor, Unicode 1.1]
-
A.
Unicode 1.1
chosen
Unicode 1.1 is an early version of the Unicode Standard that expanded character coverage by adding support for additional writing systems and symbols beyond the initial release.
-
B.
Unicode 1.0
Unicode 1.0 was the first published version of the Unicode standard, establishing a unified character encoding system that laid the foundation for modern multilingual text representation in computing.
-
C.
Unicode 5.1
Unicode 5.1 is a version of the Unicode Standard that expanded character coverage and refined existing scripts, including additional support for Cyrillic and other writing systems.
-
D.
Unicode 4.1
Unicode 4.1 is a version of the Unicode Standard released in 2005 that expanded character coverage and refined existing scripts, including support for additional writing systems and symbols.
-
E.
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.
- 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_69bd46466c7081909d07f36be2d08804 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd58dfe3508190b21836079e951a3c |
completed | March 20, 2026, 2:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bdfa26276481908d6476a94aa3e743 |
completed | March 21, 2026, 1:53 a.m. |
Created at: March 20, 2026, 1:10 p.m.