Triple
T36523086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duff's device |
E900227
|
entity |
| Predicate | usesControlStructure |
P139743
|
FINISHED |
| Object | switch statement |
—
|
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: switch statement | Statement: [Duff's device, usesControlStructure, switch statement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesControlStructure Context triple: [Duff's device, usesControlStructure, switch statement]
-
A.
controlStructure
Indicates a relationship where one entity governs, regulates, or directs the behavior, operation, or flow of another entity or process.
-
B.
typicalControlStructures
Indicates that the subject entity commonly governs or organizes the flow of execution or behavior of the object entity, as a standard or usual control mechanism.
-
C.
usesControlBlocks
chosen
Indicates that one entity employs control structures (such as conditionals or loops) provided by another entity within its logic or behavior.
-
D.
structuralControlOn
Indicates that one entity exerts structural influence or constraint over another, affecting its form, configuration, or organization.
-
E.
usedControl
Indicates that one entity exercised or applied a control mechanism or method over 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_69f76e5eedb88190a393b8c623f71dd7 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe189fec148190aeef51b417ba15b0 |
completed | May 8, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69fe17285b0881908de7569d8dbd20bd |
completed | May 8, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:11 p.m.