Triple
T1892033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Handycam |
E41893
|
entity |
| Predicate | hasControl |
P30853
|
FINISHED |
| Object | zoom control rocker |
—
|
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: zoom control rocker | Statement: [Handycam, hasControl, zoom control rocker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasControl Context triple: [Handycam, hasControl, zoom control rocker]
-
A.
canControl
chosen
Indicates that one entity has the ability or authority to direct, manage, or influence the behavior or state of another entity.
-
B.
hasControlCab
Indicates that an entity is equipped with or includes a control cab used for operating or controlling it.
-
C.
hasChangeControl
Indicates that an entity is subject to a defined process for reviewing, approving, and managing modifications or updates.
-
D.
hasAuthorityControl
Indicates that one entity possesses formal power, control, or decision-making authority over another entity or activity.
-
E.
hasControlFields
Indicates that one entity possesses or defines control-related parameters, settings, or fields that govern the behavior or configuration of another entity or process.
- 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_69a8864b6de0819098d089f6a1b910a7 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb145f96c8190a71bb9e442892e68 |
completed | March 7, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69abafe61bc48190ac9ead027df930e1 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.