Triple
T8602882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamaha YM2151 |
E203720
|
entity |
| Predicate | hasBitDepth |
P4121
|
FINISHED |
| Object | internal 14-bit or higher processing (approximate) |
—
|
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: internal 14-bit or higher processing (approximate) | Statement: [Yamaha YM2151, hasBitDepth, internal 14-bit or higher processing (approximate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBitDepth Context triple: [Yamaha YM2151, hasBitDepth, internal 14-bit or higher processing (approximate)]
-
A.
colorDepth
Indicates the bit-depth used to represent the color information of an image or display, defining how many distinct colors can be shown.
-
B.
hasDepth
Indicates that an entity possesses a measurable extent or distance from its surface inward or from top to bottom.
-
C.
hasChannelDepth
Indicates that one entity specifies or records the depth measurement of a channel associated with another entity.
-
D.
bitWidth
chosen
Indicates the number of bits used to represent or encode a given value, type, or data element.
-
E.
hasTimeDepth
Indicates that something possesses or spans a measurable extent of time, such as duration, historical depth, or temporal layering.
- 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_69ca832b56948190ba751cec255308f1 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46dc23448190a5eb63455578427e |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454eb2908190acf0e4336bc67e7b |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:24 p.m.