Triple
T11536869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rec. 2020 |
E273572
|
entity |
| Predicate | definesBitDepth |
P4121
|
FINISHED |
| Object | 10-bit |
—
|
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: 10-bit | Statement: [Rec. 2020, definesBitDepth, 10-bit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesBitDepth Context triple: [Rec. 2020, definesBitDepth, 10-bit]
-
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.
bitWidth
chosen
Indicates the number of bits used to represent or encode a given value, type, or data element.
-
C.
digitalStandard
Indicates that one entity defines, specifies, or embodies a recognized digital standard that the other entity follows, implements, or is evaluated against.
-
D.
hasChannelDepth
Indicates that one entity specifies or records the depth measurement of a channel associated with another entity.
-
E.
bitOrder
Indicates the ordering or sequence of bits within a binary representation, such as which bit positions are considered first or most significant.
- 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_69d6aae3fbec8190a14632a5df2538b6 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8839cdf688190ae75c0e6fece8e33 |
completed | April 10, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69d80879fdb48190be6dacc8aa63c809 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.