Triple
T29456580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HAM-8 display mode |
E747117
|
entity |
| Predicate | controlCodes |
P192055
|
FINISHED |
| Object | set base color |
—
|
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: set base color | Statement: [HAM-8 display mode, controlCodes, set base color]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlCodes Context triple: [HAM-8 display mode, controlCodes, set base color]
-
A.
controlCodeRange
Indicates that one entity specifies or constrains the allowable range of control codes applicable to another entity.
-
B.
controlSignals
Indicates that one entity sends or governs directive signals that determine or influence the behavior or operation of another entity.
-
C.
operatorCode
Indicates that one entity is associated with a specific operator’s identifying code used to denote who performs or manages an operation or service.
-
D.
boardCode
Indicates the specific code assigned to a board that identifies or distinguishes it from other boards.
-
E.
encodingControl
Indicates that one entity regulates, manages, or constrains the way another entity is encoded or represented.
- F. None of above. chosen
Provenance (4 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_69f0bd4125f88190b56104591351619c |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69fcf36bb86c8190a0a0ccf47cb56e5c |
completed | May 7, 2026, 8:17 p.m. |
Created at: April 28, 2026, 3:46 p.m.