Triple
T6095904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hangul Jamo Extended-B |
E135875
|
entity |
| Predicate | codeSpaceType |
P5708
|
FINISHED |
| Object | BMP extension |
—
|
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: BMP extension | Statement: [Hangul Jamo Extended-B, codeSpaceType, BMP extension]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codeSpaceType Context triple: [Hangul Jamo Extended-B, codeSpaceType, BMP extension]
-
A.
codeSpace
Indicates the namespace or contextual scope within which a piece of code, identifier, or programming element is defined and interpreted.
-
B.
codeType
Indicates the classification or category assigned to a particular code within a coding or encoding system.
-
C.
usesCodeSpace
Indicates that one entity employs or operates within a particular code space or coding environment provided by another entity.
-
D.
codeSpaceRange
chosen
Indicates the range of code points or values that define the valid span or interval within a given code space.
-
E.
hasSpaceType
Indicates that one entity is associated with, or classified by, a particular type or category of space.
- 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_69c0087cd3c48190b459848c72d84eb1 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05a9764048190ad4e9a02f9a25ab6 |
completed | March 22, 2026, 9:09 p.m. |
| PD | Predicate disambiguation | batch_69c049f5ac988190b62ba565153aaa35 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:12 p.m.