Triple
T9052080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unicode 3.0 |
E216905
|
entity |
| Predicate | hasCodeSpace |
P86098
|
FINISHED |
| Object | 0 to 10FFFF (hex) |
—
|
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: 0 to 10FFFF (hex) | Statement: [Unicode 3.0, hasCodeSpace, 0 to 10FFFF (hex)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCodeSpace Context triple: [Unicode 3.0, hasCodeSpace, 0 to 10FFFF (hex)]
-
A.
hasCodeSpaceSize
Indicates the size or capacity of the code space associated with an entity, such as the range or number of distinct codes it can represent.
-
B.
usesCodeSpace
Indicates that one entity employs or operates within a particular code space or coding environment provided by another entity.
-
C.
hasCodeIn
Indicates that one entity is represented, defined, or implemented within the codebase or coding context of another entity.
-
D.
hasCodeContext
Indicates that an entity is associated with or occurs within a particular programming or code-related context.
-
E.
hasCodeLetters
Indicates that an entity is associated with, or represented by, a specific sequence of letters used as its code or identifier.
- F. None of above. chosen
Provenance (4 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_69ca83d362e88190ae44b4e4dc194209 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc7a700de48190aa9f61d850e01cbd |
completed | April 1, 2026, 1:52 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee566b081909e3cdaf551dbd0ec |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f4f1cb48190a025d1b3d8d7a790 |
completed | March 31, 2026, 11:57 p.m. |
Created at: March 30, 2026, 7:10 p.m.