Triple
T20165255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ricoh 2A03 |
E491810
|
entity |
| Predicate | omitsFeature |
P10150
|
FINISHED |
| Object | binary-coded decimal (BCD) mode |
—
|
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: binary-coded decimal (BCD) mode | Statement: [Ricoh 2A03, omitsFeature, binary-coded decimal (BCD) mode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: omitsFeature Context triple: [Ricoh 2A03, omitsFeature, binary-coded decimal (BCD) mode]
-
A.
mayIncludeFeature
Indicates that one entity is allowed or able to contain, incorporate, or be associated with a particular feature.
-
B.
featureRemoved
chosen
Indicates that a previously existing feature has been taken out, disabled, or is no longer available.
-
C.
nonTriggerFeature
Indicates that a feature or characteristic is present but does not initiate, cause, or trigger the associated event, process, or condition.
-
D.
reasonForMissingFeature
Indicates the explanation or cause for why a particular feature is absent or not implemented.
-
E.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
- 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_69da6266c6888190bc1a3ecf24814d34 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e668442d2c81908bb1a0fac9895b5e |
completed | April 20, 2026, 5:54 p.m. |
| PD | Predicate disambiguation | batch_69e55b0c11cc8190836d1eee5945f000 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:35 p.m.