Triple
T29456632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hold-And-Modify 8 |
E747118
|
entity |
| Predicate | controlBitsFunction |
P192055
|
FINISHED |
| Object | select modify or direct color index |
—
|
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: select modify or direct color index | Statement: [Hold-And-Modify 8, controlBitsFunction, select modify or direct color index]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlBitsFunction Context triple: [Hold-And-Modify 8, controlBitsFunction, select modify or direct color index]
-
A.
controlSignals
Indicates that one entity sends or governs directive signals that determine or influence the behavior or operation of another entity.
-
B.
controlMethods
Indicates the methods or techniques used by one entity to direct, regulate, or influence the behavior, operation, or state of another entity.
-
C.
controlFeatures
Indicates that one entity has the ability to configure, manage, or influence the operational settings or characteristics of another entity.
-
D.
controlsType
Indicates that one entity has authority over, or the ability to direct or regulate, the type or category of another entity.
-
E.
controlCodes
chosen
Indicates that one entity possesses or defines codes or signals used to control, configure, or command the behavior of another entity.
- 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_69f0bd4125f88190b56104591351619c |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: April 28, 2026, 3:46 p.m.