Triple
T188923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unicode |
E3674
|
entity |
| Predicate | usesBitWidth |
P4121
|
FINISHED |
| Object | 21-bit code space |
—
|
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: 21-bit code space | Statement: [Unicode, usesBitWidth, 21-bit code space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesBitWidth Context triple: [Unicode, usesBitWidth, 21-bit code space]
-
A.
bitWidth
chosen
Indicates the number of bits used to represent or encode a given value, type, or data element.
-
B.
hasWidth
Indicates that an entity possesses a specific measurement or extent along its width dimension.
-
C.
hasCapacityType
Indicates that an entity possesses a specific kind or classification of capacity or capability.
-
D.
width
Indicates the measurement of how wide an entity is, typically the extent of its horizontal dimension from side to side.
-
E.
hasDimension
Indicates that an entity possesses a specific measurable extent or size along one or more axes (e.g., length, width, height).
- 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_69a2548debd48190ae3a06d6e65b53c6 |
completed | Feb. 28, 2026, 2:35 a.m. |
| NER | Named-entity recognition | batch_69a2594abeec8190a48f36817e647fcd |
completed | Feb. 28, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69a25672332081909386f35f3ca15dd2 |
completed | Feb. 28, 2026, 2:44 a.m. |
Created at: Feb. 28, 2026, 2:41 a.m.