Triple
T37665654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Switch 2 |
E937813
|
entity |
| Predicate | hasControllerType |
P103005
|
FINISHED |
| Object | unconfirmed (as of 2024) |
—
|
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: unconfirmed (as of 2024) | Statement: [Switch 2, hasControllerType, unconfirmed (as of 2024)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasControllerType Context triple: [Switch 2, hasControllerType, unconfirmed (as of 2024)]
-
A.
includesControlType
Indicates that one entity encompasses or specifies a particular type of control within its scope or definition.
-
B.
hasControlElement
Indicates that one entity includes or is associated with a component specifically intended to control, regulate, or influence its behavior or operation.
-
C.
typicalControllerType
chosen
Indicates the usual or most common type of controller associated with, or used to operate, a given entity.
-
D.
hasTypeOfSerialControl
Indicates that one entity uses or is associated with a specific type of serial control mechanism or protocol in relation to another entity.
-
E.
hasModelType
Indicates that an entity is associated with or classified under a specific model type.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.