Triple
T19987531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NES-101 |
E493971
|
entity |
| Predicate | powerSwitchType |
P138219
|
FINISHED |
| Object | sliding switch |
—
|
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: sliding switch | Statement: [NES-101, powerSwitchType, sliding switch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerSwitchType Context triple: [NES-101, powerSwitchType, sliding switch]
-
A.
powerOption
Indicates that one entity provides or specifies a particular power-related configuration or choice available to another entity.
-
B.
powerChange
Indicates a change in the level, amount, or state of power associated with an entity over time.
-
C.
powerInterface
Indicates that one entity serves as a power-providing interface or connection point for another entity, enabling the transfer or supply of electrical power.
-
D.
powersFeature
Indicates that one entity provides the underlying functionality or capability that enables a particular feature of another entity.
-
E.
powersType
Indicates that one entity has a specific type or category of power or ability in relation to another entity.
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65fdd1a5c8190af756632aac38bf4 |
completed | April 20, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69e537fd311881908448f2aea8b4812e |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c42c688190a22f4d31ec692377 |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 11, 2026, 3:29 p.m.